Skip to Content
Technical Articles
Author's profile photo Shivakumar Hosaganiger

Distribution of Packing Instructions as Packaging Specifications in EWM

Introduction:

The most of the times, it is common requirement to create the packing instructions in the ERP and the packaging specifications in EWM. Since these two activities will have the same functionality, it would be better to have common approach/solution to reduce the effort of creating these packing instructions/packaging specifications. The ERP and EWM systems are always in sync whenever there are changes done to the packing instructions.

 

Note – This blog was configured and tested on SAP S/4 1909 Embedded. 

This functionality doesn’t require any configurations and may require the implementations of the BADIs based on the business requirement. SAP has already implemented few of these BADIs.

Advantages:

  • The effort will be less since the packing instructions will be used as a source for packaging specifications.
  • Avoid duplications of the activities and the effort.
  • No scope for data mismatch between the packing instructions and the packaging specifications.

Deployments:

  • Decentralized EWM and Embedded SAP S/4HANA 1909 Onwards.
  • Application Component – SCM-BAS-PAK-PS

 

Prerequisites:

Activities:

Note – Be cautious while importing/activating the BC sets.

  1. BC Sets Import – Transaction Code SCPR3 

    1. Download the attachments (zip files) attached in the OSS note 2485458BC%20Sets
    2. Unzip the relevant BC sets files based on your system. Use ‘S4 BC sets’ for S/4 related BC Set activations
    3. Run the transaction code SCPR3 and then menu option: BC set –> Upload (Shift + F8) or  click on Upload IconThe system pops up with a dialog box, select the unzipped files one at a time.
    4. The system displays some message and press ‘Continue’
    5. After successful Import, the system displays the below pop up message.
    6. Assign a transport request when the system prompts with a pop up.
    7. Click on the Consistency Check (Execute) Icon or press Shift+F1 to check the activation status.
    8. Repeat the above steps for all the 5 files attached in the zip file.
    9. The system shows all the BC sets in the left side panel as imported.
  2. Activate the uploaded BC sets
    1. Run the transaction code SE38 and enter the program name ‘SCPR_ACTIVATE_SBCSETS’ and click on Execute button.

      1. Enter the BC set name imported earlier and click on execute.
      2. After execution, the system displays activation status.
  3. Validate the business function LOG_SCM_EWM_INT status
    1. Run the transaction code SFW5 and search the business function.
  4. Enable Packaging Specification field in CFM1
    1. Run the transaction code SE38 and enter the program name RCIFCUST and click on Execute.
    2. Run the program RCIFIGEN after the first step. After executing both the programs, the packaging specification checkbox appears in CFM1.

=================================================================

Testing:

  1. Create a packing instruction – POP1
    1. Run the transaction code POP1 and enter the packing instruction.
    2. Save the packing instruction with all the required information.
  2. Create CIF Integration Model – CFM1
    1. Create the integration model with the below information and selecting the checkbox for packaging specification.
    2. Execute the integration model, then the system displays the below screen with the number of packaging specifications.
    3. Click on Generate IM button to generate the integration model.
  3. Activate the CIF Integration Model – CFM2
    1. Run the transaction code CFM2 and enter the below information.
    2. Click on Execute button to display the below screen.
    3. Double click on APO application to display the below screen.
    4. Select the integration model and then click on Active/Inactive. The New Status will be changed to Active.
    5. Click on Start to trigger the integration model. If there are no errors, the data will be transmitted to the EWM system.
  4. Verify the packaging specification in EWM system
      • Run the transaction code /N/SCWM/PACKSPEC and enter the packing instruction distributed from the ERP system.
      • Click on Execute. The system display the below information.
      • Click on Display Icon to display the packaging information.

Observations:

    1. The distributed packaging specification is inactive status (Mostly a BADI exists for this to activate after the distribution. Need a more analysis).
    2. After initial transfer, the standard implemented BADI automatically distributes the packing instructions whenever the changes are saved.

References:

 

Conclusion:

With this functionality, the packing related information in ERP and EWM is always sync. This will reduce the effort of creating the packaging specifications and packing instructions separately.

If there are any changes done to the packing instructions, the system automatically syncs them with the EWM packaging specifications.

 

Your suggestions/feedbacks are highly appreciated. There are few more articles on the way. Please follow my profile for the new blog posts related to latest features provided by SAP.

Do you have any further comments related to this topic? Do share them in the comments sections below without any hesitation. You can also ask questions in the SAP EWM Master Data  Community Q & A Section

Note – All the images are created by me and free to use/share.

 

Thanks for your feedback and support for the previous articles.

 

Happy reading.

 

Regards,

Shiva

Assigned Tags

      13 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo SAURABHA SRIVASTAVA
      SAURABHA SRIVASTAVA

      Great Document and beautiful explation. Document gives very good insight.

      Author's profile photo Shivakumar Hosaganiger
      Shivakumar Hosaganiger
      Blog Post Author

      Thank you 🙏

      Author's profile photo manic manic
      manic manic

      The information was really useful.Great explanation and detail step helps a lot in understanding SAP EVM AND ERP..Keep the good work and post more useful topics like this

      Author's profile photo Shivakumar Hosaganiger
      Shivakumar Hosaganiger
      Blog Post Author

      Thank you 🙏

      Author's profile photo Daniil Mazurkevich
      Daniil Mazurkevich

      It makes sense to add that it works well only in simple cases. Structure of these object is different, therefore it is not possible to have a proper mapping. Distribution on ERP side is not so good as for example material master, there are relative big gaps in the implementation of the interface.

      Author's profile photo Shivakumar Hosaganiger
      Shivakumar Hosaganiger
      Blog Post Author

      If we keep thinking like this, then SAP never comes to know these limitations. Unless we find them and highlight them, it would be difficult to get these addressed. You can refer to reply provided by Moin.

       

      Author's profile photo Daniil Mazurkevich
      Daniil Mazurkevich

      SAP Knows it, we communicated it during the project. And I am not talking about issues which are possible to solve with a BAdi. SAP is focused on UPD I guess, and therefore gaps in the PS distribution won't be solved.

      Author's profile photo Moinuddin Sha Quadri Khairuddin
      Moinuddin Sha Quadri Khairuddin

      Hello,

      A couple of BAdIs are available for data mapping. In the ERP side one could use the BAdI cif_enhance_packspec to manipulate the packaging instructions data (the complete Packaging Instruction data is available for manipulation).

      On the SCM side, the BAdI /scwm/cif_ps_inbound could be used to manipulate the various parts of the packspec like (Header, Level, Content and Element). If no mapping is done in this BAdI, the logic uses the default values like 'SAP' for Packaging Specification group, 'LS01' for Level Set and 'LT01' for Level Type.

      To enhance the condition records, BAdI /SCWM/CIF_PS_SCM_CT_ENHANCE could be used. Check the fallback implementation for this BAdI and it allows custom mapping at two levels, one is the condition tables mapping between ECC and SCM and the second is the field level mapping. The default implementation has hardcoded values. You can build a custom table/BRF+ Table etc.. to map the condition table between ECC and EWM. To map the fields, the fallback class of the BAdI uses a custom helper class to do custom mapping between ERP and SCM. The fallback class can provide a cue on how to do field level mapping. The standard does the mapping between plant and SLoc with warehouse, material to product, vendors and customers to BP etc.

      Depending on your landscape, you can activate the BAdI Implementations for BAdI /SCWM/CIF_PS_CONDITION_PROCESS. By default the BAdi Implementation /SCWM/CIF_PS_SCM_CONDTECH is activated which is meant for EWM (The result is the Condition technique table entries that EWM understands). If you are on a SNC(ICH) system, you can activate the BAdI implementation (/SCWM/CIF_SNC_CONDITION). The result is the the condition table entries that SNC understands.

      Regarding having "InActive" Packaging Specifications, since you did not implement any custom mapping in the BAdI (neither in ERP or the SCM BAdI), the system would have determined the standard delivered PS group "SAP". I believe the standard delivered customizing for the PS Group "SAP" is not to activate the PackSpec automatically (IMG: Packaging Specification -> Define Packaging Specification Group). That is why your packspec was not "Active".

      The tool is only a framework for transferring the packaging instruction data. However, when the provided BAdIs are used, the framework becomes a highly flexible and efficient tool.

      Author's profile photo Shivakumar Hosaganiger
      Shivakumar Hosaganiger
      Blog Post Author

      Thanks for the detailed information. It is good to know such enhancements and the improvements provided by SAP.

       

      Let me deep dive into it and try updating this post.

       

      Author's profile photo Mageshwaran Sivasamy
      Mageshwaran Sivasamy

      "If there are any changes done to the packing instructions, the system automatically syncs them with the EWM packaging specifications."

      Any suggestions on how to achieve it.

      We are using embedded EWM.

      Author's profile photo Moinuddin Sha Quadri Khairuddin
      Moinuddin Sha Quadri Khairuddin

      Hello Mageshwaran,

       

      When the BTE is activated, the online transfer of packaging instructions should happen automatically. It happens when the packaging instruction data is changed at either of the 2 places:

      1. When the packaging instruction is changed in POP2 or

      2. When the condition is changed in POF2.

      Best Regards,

      Moinuddin

      Author's profile photo Surendra Seemakurthi
      Surendra Seemakurthi

      Great. Ver nicely explained. Thanks Shivakumar.

      Author's profile photo Shivakumar Hosaganiger
      Shivakumar Hosaganiger
      Blog Post Author

      Thanks Surendra.