Download SAP SD - Strategy for Product Allocation Master Data Management PDF

TitleSAP SD - Strategy for Product Allocation Master Data Management
TagsTechnology Strategic Management Computing Information Technology Management
File Size150.9 KB
Total Pages7
Document Text Contents
Page 5

Strategy for Product Allocation Master Data Management

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

© 2009 SAP AG 5

Standard SAP transaction like OLIX (Copy Delete versions of info-structure) can be used to manage
data in the info-structure like archiving the current data to another version (say 901) before the actual
data in version 000 is changed.

The Strategy here is to manage large changes like revision of product allocation set-up via mass
processing programs (like the Tool A) in addition to the copy routines created in MCSZ. Small
changes to data, like addition of a new customer, should be handled via standard SAP transactions
like MC62 (change planning Hierarchy) and MC94 (change plan in flexible planning).

3. End-of Season Archive – Review & Archive of previous season Data

The end of a sales season brings up a lot opportunity to review the performance of the past sales
season and reconcile the learning from the past season. The data from the past season can at this
point be archived, by removing it from the actual version 000 to some other version (or info-
structure). The archived data can be utilized for analysis and reporting. The same data can also act
as a starting point for the preparation of next year Product Allocation Master Data. This is useful as a
starting point rather than starting from scratch.

The standard SAP tool like OLIX (Copy Delete versions of info-structure) is again an effective tool to
manage this business requirement. In addition, custom applications can be built to download the
previous year data into a template directly that the Allocation manager can use to work on the next
year numbers.

Other Success factors

There are some other ergonomic aspects that can be incorporated in the design strategy that proof
effective when working in such scenarios. These are not specific to Product Allocation Data
management but can be applied to any scenario equally. These small points will make work easier
and improve efficiency.

1. Always develop adequate reporting on Product Allocation master data and have proper error
handling for the custom objects created.

2. As the data being handled for product allocation can be humongous it always benefits to have
background execution option in most of the custom reports being developed.

3. When working with background mode of execution plan for interface with attached UNIX system to
enable working even when you are not online.

Page 6

http://help.sap.com/saphelp_47x200/helpdata/en/93/744d05546011d1a7020000e829fd11/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/93/744d05546011d1a7020000e829fd11/frameset.htm
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d0c0b890-ac75-2b10-d8ad-b8cecdea8d3f
https://www.sdn.sap.com/irj/sdn/nw-mdm

Similer Documents