SOLAR02 use to attach documents to Process Step (L6), or Process (L5) if there is no L6.
•Solution manager update steps:
Identify process steps in AMAT_MAINT Follow the document naming convention
Update SolMan information in the PCR Assign the correct key word
Attach document to correct tab Set the correct status for AAB, Review
Check document type and template Set the correct status for closure, Released
Attach the end user transactions for the process 5 Attach QA, Regression
to the Transactions tab. Can add URLs and Key and UAT testing to the
WebDynpros. Double click to access in Dev tabs Test Case tab.
Use the properties button to
set the Status and Key Word, also
change Title and Document Type
Status must Update
be set correctly the SolMan
Attach one Attach the Unit Test under each If more than one process prior to moving section in
config/spec IMG node and Technical object. step is impacted link the to QA or Prod the PCR
document per IMG Use a link to use a single test documents to the
node and per script, all links point to a single additional process steps.
Technical Object document for update Link do not Copy!
Help documentation:
uPerform: [Link] Global Information Services Solution Manager (SolMan) PCR
Livelink: [Link] 1. Enterprise Corp Wide CoP Business Transformation
Library SAP Competency Center SAP Solution Manager SolMan Training
Remedy: Submit ticket to SAP Solution Manager Support queue
Applied Materials Confidential
SOLAR_EVAL use to search for documents attached to process steps and update the status
Path to correct search tool: Analysis Project Configuration Assignments Documentation
Identify the impacted Status has to be updated to move Most document Documentation needs to
Process Step Level (L6) COPY EDITINGBeing processed in Development types have AMAT be attached to the correct
or the Process Level IN PROGRESS Request Transport to Quality templates which tab. Use links to attach
REVIEW Request Transport to Production
(L5) if there is no L6. RELEASED Validation Complete in Production
must be used document copies.
L1
L2 For the BPD upload the If more than one For SAP Do not use older For Integration,
L3 Domain BRD for an OA process step is (OSS) Notes formats for config Regression and UAT
L4 or enter description from impacted link the upload a PDF and functional testing OK to upload
L5 HD ticket into template docs to all steps of the note spec documents Unit Test format
L6
Follow the document naming standard Text description, include
Letters “PCR” and PCR number with no gap
PCR12345_A_OBJECT_NAME_Description region code for regional
regression testing
Object type, if in doubt use A
A - Application Configuration For the Business Process Description use the OA or HD number For Regional
R - Report
I - Interface For SAP (OSS) Notes use the note number Regression Testing
C - Conversion For configuration reference use the IMG Object name append the region
E - Enhancement code, e.g. AMC or
W - Workflow For technical and functional specs use the Technical Object name AME, to the object
F - Form For test documents combine the lead config object and lead technical name.
object names
Applied Materials Confidential