Skip to Content

Hi Folks,

In continuation to my earlier post on Interfacing AFS to Retail systems, I would like to present the solution for Size Migration for the existing Product issue within SAP AFS space.

What is a Size in AFS?

A size is specific to a Material. It is dynamic and volatile according to AFS Business scenarios. It is linked with UPC as well as Sales Grids and PO Grids in AFS system.

What is the system behavior when we migrate a size from AFS to Retail?

As we all know that the key function for ALE is Change Pointers.

There is a standard program – RBDMIDOC_RETAIL which processes the AFS Change Pointers and sends it to IS-Retail in the form of ARTMAS IDOC. But there are technical glitches related to few hard codings in place, such as – Condition Types, Change Pointers Table etc.

Technical Info

We have worked with AFS Experts from SAP AG, and came up with a solution to deal with the customers who migrated their Change Pointers table from BDCPV to BDCP2/ any custom table. I would like to share the OSS Note – 1624203. Implementing this Note should take care of addressing the hard coding of BDCPV within the standard program. SAP has provided the OSS note # 1741591 will replace this hard coding and allow to process Customer specific condition types using a BADI /AFS/RETAIL_CDPOS.

ARTMAS Packeting function module ‘Z_MM_RTL_ARTMAS_CHPTR_PKT’ will be enhanced to pick up sales grid changes  (/AFS/GRID object changes)

/wp-content/uploads/2013/10/1111_294267.jpg

Inference

Few customers who still uses standard ‘Out of the Box’ solutions in Interfacing AFS to Retail, now have options to add more Condition Types related to PO Grids and Sales Grids after implementing this OSS Note.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply