In order to invoke the PLMSI services without a connected external PLM system you can use transaction /iwfnd/gw_client to invoke the REST services.
Please be aware that you may create a mismatch between the external PLM system and SAP if you store e.g. the processing status back to the external PLM system and built some logic on that. (e.g. setting a release status based on processing result).
Steps within transaction /iwfnd/gw_client:
- Maintain HTTP “POST” for *MaintainRequest / in case of *ReadRequest maintain “POST"
- Maintain Request URI as mentioned above for the required MDM entity (e.g. for PV: /sap/bc/rest/plmf/plmsi/0002/ProductVersionMaintainRequest)
- Enter the content-type with “application/json”
- Maintain the MDM payload into the left lower section. ( Hint: you can send the same payload multiple times. You need to make sure that the messageId is unique. So the easiest way is to count up)
- Press "Execute"
- In the pop-up just confirm
- Result is displayed in the right section
Required information:
SAP Release | Base URL |
SAP S/4HANA | /sap/bc/rest/plmf/plmsi/0002 |
SAP ERP | /sap/bc/rest/plmf/plmsi/0002 |
The relative URLs are dependent on the REST entity or action name:
BO Type / Action | Relative URL |
ProductVersion | /ProductVersionMaintainRequest |
- Read Request | /ProductVersionReadRequest |
DocumentVersion | /DocumentVersionMaintainRequest |
- Read Request | /DocumentVersionReadRequest |
StructureVersion | /StructureVersionMaintainRequest |
- Read Request | /StructureVersionReadRequest |
ChangeObject | /ChangeObjectMaintainRequest |
- Read Request | /ChangeObjectReadRequest |
VariantDefinition | /VariantDefinitionMaintainRequest |
VariantOption | /VariantOptionMaintainRequest |
VariantOptionRule | /VariantOptionRuleMaintainRequest |
ProductionOperationList | /ProductionOperationListMaintainRequest |
ProductVersionKey | /ProductVersionKeyReservation |
Vendor | /VendorMaintainRequest |