Issue while creating Mass Pack Specification through Standard Tcode "/SCWM/IPU"

[#1]

I am facing issue while I am creating the Pack Specification from Standard Tcode "/o/SCWM/IPU"

In an excel sheet I gave multiple Pack Specification records and tried creating it. 
But the issue happening is:

1. If there is an error for one of the level, the record is still created instead of the program stopping.
2. And, even if I resolve the error in the Excel file and then reupload the same file, it is creating a new duplicate record instead of Changing the existing record that was created

Is there any other method to load Mass Pack Specification instead of using the Standard Report?
The Standard Report that the Tcode calls is "/SCWM/R_PS_DATA_LOAD"

[dawid90]

Dear @Vedant_Chaudhari,

The standard SAP-supported approach in this area is Packing Instruction maintenance through the standard apps, plus the released Packing Instruction Read, Create (A2X) API. SAP documents Manage Packing Instructions Master Data for searching existing packing instructions and navigating to create/edit and it documents the Create Packing Instruction process in Public Cloud as well. For the specific issue with /o/SCWM/IPU and report /SCWM/R_PS_DATA_LOAD this means that in Public Cloud this upload should not be positioned as the standard tool for ongoing mass change or upsert of existing records

The key point is that the released API is documented as Read, Create (A2X) and its documented operations are creation-oriented. Accordingly the standard Public Cloud design supports:

• creation of new packing instructions via API and
• maintenance of existing packing instructions in the apps
  rather than a standard Excel-based mass upsert/update process with rollback or stop-on-error behavior for this object

As a result this process should not be positioned in Public Cloud as a standard mass maintenance mechanism with full rollback or stop-on-error behavior. Likewise, re-uploading corrected data should not be treated as a standard method to change an existing record so creation of a duplicate is consistent with a create-oriented process

More details below:

https://help.sap.com/docs/SAP_S4HANA_CLOUD/32da8359c8ee4e8b8e8c5e15cacba5aa/60c80a4601c340b983cdba5c...

https://help.sap.com/docs/SAP_S4HANA_CLOUD/32da8359c8ee4e8b8e8c5e15cacba5aa/6c5db9537cceb44ce1000000...

https://help.sap.com/docs/SAP_S4HANA_CLOUD/32da8359c8ee4e8b8e8c5e15cacba5aa/758cbf53f106b44ce1000000...

https://help.sap.com/docs/SAP_S4HANA_CLOUD/9ce855c709ce4f5c99b685903461106e/8c64ea338f6a4c68b40f8dbc...

The recommended workaround is:

• use Excel only as an external staging file
• check first whether the packing instruction already exists
• send new records through the released API
• and maintain existing/corrected records in Manage / Change Packing Instruction instead of re-uploading them as new

Summary:

In Public Cloud, the supported model for this object is standard app maintenance for changes and Read/Create API for new records. Therefore the recommended design is API-based creation for new packing instructions and app-based correction of existing ones, rather than file-based mass upsert through /SCWM/R_PS_DATA_LOAD

Best Regards,

Dawid

[Vedant_Chaudhari]

What about the Private Cloud Edition is it possible in that?