Hello Community.
We are testing an FIORI app using RestAPI Odata and SOAP integration to get material data from external data provider using this methods and classes. But we find this challenges using the most complete services with all views available for material (pre-defined material number as mandatory field).
- Are there any alternatives and /or workaround to solve a problem with this SOAP Product Service Inbound regarding a mandatory filled field for Material ID using this method. We don´t want to determine a material ID on this stage (Change Request) and prefer to use a temporary number for material like standard procedure in manual change request creation (CR Type MAT01).
W We are using (see below) SOA Product Service and DRF to implement this integration like SAP Help below (ProductMDMBulkReplciateRequestIn):
On the other hand, by standard procedure, from Webdynpro screen, the system uses a temporary number for material ($xx) and the final number is give only at the end of workflow and final activation. The system uses a number range in ERP side (S/4HANA) to get material ID and update this final number back to a respective Change Request on SAP MDG.
Any ideas about how we can avoid a mandatory material ID determination and use a temporary material number as usual?
Thanks