APO DP disaggregation

Hi Gurus,
Of the both disaggregation types the structural disaggregation( as a example region as a aggregation level and customer/dc etc as the detailed level using calculation type) and the time-based disaggregation, which one happens first..
Please share your ideas.
Reards,

Hi,
As such there is no sequence in between Time-Based and Characteristic-Based dis-aggregation.
This depends on the business needs that Dis-aggregation of the planning data should be done on the bases of characteristics (like product brand or sales region) or it should be dis-aggregated with respect to time level ( say month wise data dis-aggregated to weeks). This is done at KF level and is defined at the time of PA creation.
Anyone can be used first or both can be used.
Thanks

Similar Messages

APO DP: Disaggregation to product&plant level from higher levels.

Hi.
We do demand planning on groups of products and for country/region in general, we have around 48.000 CVC's in our current setup. It works very well.
A new situation has arisen where we need to have the forecast split down to product and plant level.
As is we simply don't have the information at this level of granularity.
I don't see how we can add for instance product to our setup, we have around 20.000 products so the number of CVC's in DP would become massive if we did this.
I was thinking that perhaps something could be done by exporting the relevant key figures to a new DP setup with fewer characteristics (to keep the number of CVC's down) via some infocubes, perhaps some disaggregation could be done via some tables and the BW update rules. This still leaves the issue of how to get the figures properly disaggregated to plant and product though.
Does anyone have experiences on how to get the figures split to lower levels from DP when you're planning on a higher level?

Simon,
One approach as you mentioned can be creating Z Table where in you set up disaggregation proportion from product group level to product level or product location level.
Product Group X 100 Product A@loc1 10
Product B@loc1 90
Download your planning area data into infocube C and then use BW routines to convert the data from group in infocube C to lower level refereing Z Table....into another infocube..
SAP also provides such standard functionality of spliting the aggregate Demand plan to detailed level
SNP plan..through functionality like location slit or product split.
Essential you will be using same concept in yor BW solution or you may also want to consider the
release your DP to SNP planning area its as solution of diaggregation of data to lower level.
Regards,
Manish

APO DP Disaggregation issue.

Hi All,
Dis-aggregation issue in Demand planning forecast execution. History 3 material, CVC Combinations 6 material, Matching
History and CVC 3, when i execute Forecast, disagrregated to all 6 material. i want only 3 materila dis-aggregation APPODPDANT
i used for Disagrregation,please help me

Hello,
If I understand correctly, you want to use proportional factor to disaggregate the calculated forecast, right?
Please first make sure that the proportional factor APPODPDANT is correctly calculated based on the history key figure.
Make sure the APODPDANT's values are zeroes for those CVCs without historical data.
(You can check APPODPDANT key figure's value by putting it into a certain dataview.)
If the proportional factor is not correct, please recalculate it in /sapapo/mc8v.
Then please make sure that the disaggregation type of the forecast key figure is correctly set. It shoud be:
1)Disaggregation type should be 'P' instead of 'I'. ('I' is also OK, but for testing purpose, 'P' is better.)
2)Disaggregation key figure is set as APODPDANT.
3)Time based disaggregation should have the same setting as structural disaggregation.
At last, the forecast run in foreground should be run at aggregated level.
Best Regards,
Ada

APO Aggregation and Disaggregation error

Hello Experts,
This is related to APO. We have some Key figures which are set as "Aggerigate" in Planning Area. And when we fetch that data in Cube, all the KF's in cube are of Summation(SUM) type in aggregation tab. Now what happening is that we are getting all the data in the PA as aggregate and in Cube it gets summed up, our requirement is that data in cube should match with PA. I think this error is due to the Average in PA KF's. But we have to keep the aggregate in PA and need to have same data in Cube.
for example, for month 072010 if we have valeu in key figure of planning area for product as:
Product :       KeyF Value(Aggregate)
A                       3
B                       3
C                       3
total                   9
this value in cube is appearing as : 9 for all the three entries. and we want it to be 3 only.
Based on this I have to build some queries which should have value as 3.
if we are not able to achieve it in Cube then is there any way to achieve it in Query itself?
Can you please help me out to achieve this?
Thanks
Am
Edited by: Amit Dahiya on Jul 22, 2010 5:39 PM

Aggregation: A value summed up on a characteristic (or a combination of those). Eg. aggregation of sale of Red colored and blue colored Manual stickshift cars could be aggregated in color characterisic to give us sale of all Manual shift cars. Similarly aggregation of sale of Red colored manual and red colored automatic cars on the transmission characteristic could give you sale of all red colored cars.
Similarly disaggregation of proportioning values from a higher to a lower level. Eg. sale of all red colored cars could be disaggregated 50:50 to manual and automatic transmission cars.

APO DP SCM 5.0 Disaggregation issue + performance guide

Hi All,
I am again facing a u201Dsmallu201D disaggregation calculation issue. What I am trying to do is to calculate Corrected sales history to the most detailed level through disaggregation.
KF1: Sales history
KF2: Correction
KF3: Corrected Sales history
Situation:
The calculation is performed via background job:
Aggregation level:
Country
Sales org.
Product
Selection:
Country: 001
Sales org: 2000
Product: 12 & 13
I use macro for the calculation:
Start
Step1: KF3 = initial
Step2: KF3 (redisaggregation) = KF1 (Values) u2013 KF2 (Values)
End
Planning Area:
KF3: I (if initial, based on a another keyfigure) u2013 KF1 , Time based disaggregation (not relevant)
How can I get KF1 based disaggregation for KF3? Is it even possible with the above solution or should I come up with a totally different approach to this? Calculating in the most detailed level is not possible because the system canu2019t handle so many CVCu2019s. Although I kind of wander that, the system is almost a beast and it can only calculate 50000 CVCu2019s in a 5 hour? Any suggestions on this one also?
Thanks in advance,
Juha

Hi Manimaran,
I just tested your suggestion and the results are:
Sales history KF1:
SUM: 1000
Product: A: 750
Product: B: 250
Product A for Customer 1: 325
Product A for Customer 2: 325
Product B for Customer 1: 125
Product B for Customer 2: 125
Correction KF2:
SUM: 1000 (automatically split via disaggregation, this number is inserted in planning view and after this the background job is executed)
Product: A: 500
Product: B: 500
Product A for Customer 1: 250
Product A for Customer 2: 250
Product B for Customer 1: 250
Product B for Customer 2: 250
Corrected Sales history KF3 (after background job and disaggregation):
SUM: 2000
Product: A: 1250
Product: B: 750
Product A for Customer 1: 625
Product A for Customer 2: 625
Product B for Customer 1: 375
Product B for Customer 2: 375
As I analyzed this it seems like it is disaggregating it evenly? I have checked that the planning area settings are:
KF3: P - (based on a keyfigure) Keyfigure: KF1
so on that basis there should be no even disaggregation. I also tried with different aggregation level settings but the results are the same.
BR,
Juha
Edited by: Juha Pajarinen on Aug 12, 2011 11:37 AM

Disaggregation in APO DP

I am using APO DP version 5.
In my planning object structure I have product group and product characteristics.
I have a key figure called % adjustment. If the user enters, for example, 10 in this key figure at the product group level, I want this figure of 10 to be applied for each product in the product group, via a macro where a percentage adjustment of 10% is applied to an unadjusted key figure (at the product level).
The question is - what calculation type should be used for the % adjustment key figure so that the value entered at the higher level is simply replicated down to the lower level?
Thanks, Bob Austin

Use calculation type 'A' - average. Easy way to populate values is enter (manual or macro or job) this KF value at the highest possible agg.level. Same value get copied to lower level automatically. But you should be careful when add new CVCs, as this is a average type, it calculate by adding all KF values then dividing number of CVCs in next level. If new CVCs added then (as this KF value is zero) the value will not be same. (for eg 10.000% will become 9.9% depending on number of CVCs). So when new CVCs added you need to zero out and re-enter samevalue at agg. level.
Hope this helps,
Niranjan

Bw-apo consultant roles n responsibilities?

hi,
i am a bw consultant.i just want to know what are the roles n responsibilities of a bw-apo consultant.

Hello PADMAVIJAYA M,
I am in a similar role right now. In this role, you might be in charge of any of the following:
1) Design and implementation of components for extraction of data from source systems and loading of data into APO structures. For example, in APO Demand Planning, sales history is retrieved from a source system (e.g. SAP ERP, Oracle, Flat File) and then placed into a temporary InfoCube in the APO server. The data from this InfoCube is then used to load data into the DP Planning Area. It can also be used to generate Characteristic Value Combinations (CVCs).
2) Design and implementation of components for extraction of data from APO structures (and then loading that elsewhere). For example, in APO Demand Planning, you will be in charge of extracting data from the Planning Area (using the datamart interface) and then processing that (e.g. aggregating/disaggregating the data into the required hierarchy level) or loading that to an external BW server (e.g. an Enterprise DW).
3) Reporting (i.e. using BeX)
For example, you might be asked to design reports in BeX that for example, might compute the discrepancy of the sales history VS the forecast..
There is usually a large volume of data that comes from APO and we have to make sure we manage the performance aspects.
In summary, I guess this is "typical" BW Consultant work except that you are dealing with an APO system as the target/source.
Hope this helps

Updating of data in APO DP - what is 'best practice'?

I am using APO DP V5.
I am using XI as an integration broker to receive data from external sources which is to be loaded into APO DP.
There are of course different ways of doing this, for example:
1. From XI, pass an XML message which then loads a delta queue in APO BW, loads an InfoCube, which is then used to load data into an APO planning area
2. From XI, pass the data into BAPI parameters, which are then used to directly update data in an APO planning area via a BAPI call (eg BAPI PlanningBookAPS)
What is the recommended 'best practice' here?
Thanks,
Bob Austin

Hi Bob,
I do not have experience in SCM 5.0 and XI but shall give my views from general experience.
What kind of data you are loading in APO DP is the driver for the two ways mentioned by you.
Traditionally (older versions of SCM/APO and non XI interface) Sales History is captured into an Infocube and then loaded to DP Planning Area. The reason - you normally use this Infocube for generation of CVCs which is the Master Data in APO DP. Moreover you will use this data to generate Proportional Factors for disaggregation of Statistically generated Forecast at aggregate level to the lowest level. So there is a requirement for loading Historical data from external systems to APO DP via an Infocube.
The other kind of data would be market and sales forecast. This is a timeseries data which need to be directly loaded to the Planning Area for immediate Interactive Planning. In that case rather than putting it in an Infocube and then periodically loading the data from the Infocube to the Planning Area, its better to load the data directly in the Planning Area. There the BAPI will be a good option.
Hope this gives some ideas to your query.
Thanks,
Somnath

Disaggregation Best Practice

Hello,
What are the best practices for disaggregation in APO? Is there any good documentation for when to use each type of disaggregation? If so, please forward to me. Can anyone explain exactly how the "generate proportional factors" program in APO works? If I only used the S-Pro rata method and I have existing data at the lower levels, do I even need to generate proportional factors in order for disaggregation to work correctly?
Thanks

Hi
The SAP APO help on <a href="http://help.sap.com/saphelp_scm50/helpdata/en/66/29fb672fbe11d398240000e8a49608/content.htm">Generation of Prop factors</a> would be helpful
Also read the link from there on the disaggregation
Proportional factors are used as a common base, in order to do realistic disaggregation in cases where you dont have data for all levels. They are generated based on historical (or in some cases planning) data
and stored in the KF for prop factors- APODPDANT
In planning area setuyp you set some KF to disaggregate based on another KF or APODPDANT.
you dont have to generate prop factors if you dont have I or P in your KF aggregation type

SAP SCM and SAP APO: Best practices, tips and recommendations

Hi,
I have been gathering useful information about SAP SCM and SAP APO (e.g., advanced supply chain planning, master data and transaction data for advanced planning, demand planning, cross-plant planning, production planning and detailed scheduling, deployment, global available-to-promise (global ATP), CIF (core interface), SAP APO DP planning tools (macros, statistical forecasting, lifecycle planning, data realignment, data upload into the planning area, mass processing u2013 background jobs, process chains, aggregation and disaggregation), and PP/DS heuristics for production planning).
I am especially interested about best practices, tips and recommendations for using and developing SAP SCM and SAP APO. For example, [CIF Tips and Tricks Version 3.1.1|https://service.sap.com/form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700006480652001E] and [CIF Tips and Tricks Version 4.0|https://service.sap.com/form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000596412005E] contain pretty useful knowledge about CIF.
If you know any useful best practices, tips and recommendations for using and developing SAP SCM and SAP APO, I would appreciate if you could share those assets with me.
Thanks in advance of your help.
Regards,
Jarmo Tuominen

Hi Jarmo,
Apart from what DB has suggested. you should give a good reading on the following.
-Consulting Notes (use the application component filters in search notes)
-Collective Notes (similar to the one above)
-Release Notes
-Release Restrictions
-If $$ permit subscribe to www.scmexpertonline.com. Good perspective on concepts around SAP SCM.
-There are a couple of blogs (e.g. www.apolemia.com) .. but all lack breadth.. some topics in depth.
-"Articles" section on this site (not all are classified well.. see in ECCops, mfg, SCM, Logistics etc)
-Serivce.sap.com- check the solution details overview in knowledge exchange tab. There are product presentations and collaterals for every release. Good breadth but no depth.
-Building Blocks - available for all application areas. This is limited to vanilla configuration of just making a process work and nothing more than that.
-Get the book "Sales and Operations Planning with SAP APO" by SAP Press. Its got plenty of easy to follow stuff, good perspective and lots of screen shots to make life easier.
-help.sap.com the last thing that most refer after all "handy" options (incl. this forum) are exhausted. Nevertheless, this is the superset of all "secondary" documents. But the maze of hyperlinks that start at APO might lead you to something like xml schema.
Key Tip: Appreciate that SAP SCM is largely driven by connected execution systems (SAP ECC/ERP). So the best place to start with should be a good overview of ERP OPS solution overview, at least at the significant level of depth.). Check this document at sdn wiki "ERP ops architecture overview".
I have some good collection of documents though many i havent read myself. If you need them let me know.
Regards,
Loknath

Planning area dp apo

hi
guru
so i have created PA. and also time series created for it.. and also PB DV created for it..
now i want to add a KEY figure to that PA??? is that POssible? how i should i add a kf to PA????
the same senerio to MPOS and PB????

Hi dallyanusha,
I think there are series of questions. I will try to cover few of them.
1) Transfer of data from R/3 to APO.
In SAP, data transfer from R/3 to APO will be through Core interface.
2) Transfer of data from R/3 to BI
This will be done by building infoobjects like infocubes in BW and
store R/3 data in cubes
3) Fixed key figure value
Contains the key figure, in which the fixed value of the basic key figure is saved.
4) Use of Fixed key figure value
While planning a key figure, you can wish to protect the planned value against any overwriting. The value can be fixed in the planning table. The fixed key figure is required to store this information. The fixed basic key figure value is copied down to the finest detail into this key figure. The information with this is available on an aggregated level as regards what share of the key figure is fixed and must not be changed. If the share is 100% then the key figure must not be changed by planning functions. If the share is between 0& and 100% then the value may only be changed in a restricted way. The change is only disaggregated on those details that are not fixed.
Regards
R. Senthil Mareeswaran.

APO DP - lifecycle planning

I am using APO DP V5.
I am forecasting at a monthly level, then performing time based disaggregation down to weeks.
So, when performing forecasting using lifecycle planning, the 'phase in'/'phase out' profiles are of course working at a monthly level.
But in fact I want to be able to model the 'phase in'/'phase out' within a month, ie at weekly level.
So, for example, suppose at monthly level, the 'phase in' results in a forecast qty of 0 for month n, and 100 for month n1. But in month n1 I actually want to see quantities of 25, 50, 75, 100 at the weekly level.
Any ideas about how I could do this? I'm thinking about careful use of time based disaggregation factors for instance.
Thanks, Bob Austin, Atos Origin

I would suggest you to havetwo Data views -one in Month and the other in Week. You can have two Forecast Profiles, that are defined that works on weekly and monthly levels. The former can have LC active and the latter may not. These two profiles will create monthly and weekly forecast keyfigures respectively. While doing time disaggregation of monthly forecast keyfigure, use the weekly forecast keyfigure for disaggregation.

Navigation attributes in APO DP

I am using APO DP V5.
I have a planning characteristics of product and customer. I also have a characteristic of 'product group'. I am trying to clarify the real difference between modelling this characteristic as a planning characteristic or as a navigation attribute of product.
Based on my testing, using product group as a navigation attribute, I can select by product group and apply fixing and disaggregation.
So, what is the 'added value' of modelling 'product group' as a planning characteristics?
Any feedback appreciated.
Thanks, Bob Austin

To quote OSS note 413526
When defining a planning area you have the option of using either basic
characteristics or navigation attributes. With regard to the design the
following aspects should be considered:
Navigation attributes:
===========================================================
The use of navigation attributes adversely affects performance during
data selection and during navigation in the interactive planning. The
number of used navigation attributes is important and not the different
specifications of a navigation attribute.
It is very easy to realign the planning objects since only the master
record table of the affected InfoObject has to be changed.
Navigation attributes can not be used as a characteristic during the
definition of a fixed aggregate.
During the disaggregation a navigation attribute can never represent the
lowest planning level.
Navigation attributes can not be used in the promotion planning, in
other words an 'assign object' is not possible for navigation attributes.
Basic characteristics:
===========================================================
In comparison with navigation attributes, the exclusive use of basic
characteristics improves the performance.
It is possible to realign the planning objects, but this is more
complicated.
Basic characteristics can be used during the definition of aggregates.
Both navigation attributes and basic characteristics can be used during the
data extraction.
It is therefore not possible to give a clear-cut recommendation for or
against navigation attributes.

Abaper role on APO

Hi Experts
Iam working as senior abap consultant. iam new to APO ,could please tell me what is the role of abaper in APO in development perspective ?
please send me any devloped or sample objects on APO ( which involves abap devlopment).
mailid: [email protected]
your favour will be highly appriciated.
thanks in advance
regards
sri

Dear Sri,
You would need to upload master and transaction data. BW skills would also be advantageous as it would deal with data extraction using administrative workbench.
APO Technical:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/scm/apo-technical&
FMs available:
BAPI_POSRVAPS_SAVEMULTI3 - Delivery - ATP Category BR in APO DRP
BAPI_PBSRVAPS_DETAIL2 - Planning Book data - Input Parameters Planningbook, Data_view, Planning_Version, Period_Type Values (as in the domain /SAPAPO/CPDS_PERIOD_TYPE e.g. 'B' Week 'C' Month), Date_From and Date_To (format e.g. ww.yyyy)
/SAPAPO/EFPL_ORD_NET_GET - Pegging relationship - For pegging relationship across the entire strucuture
EXIT_/SAPAPO/SAPMMCP6_005 ZXDMUSERU05 - User exit - macro Add code in ZXDMUSERU05
/SAPAPO/RRP_LC_PEGID_GET_IO - MRP Data from Live Cache - to get the data from live cache. Pass the pegid to the export parameter 'it_pegarea'. Determine pegid by using the function module '/SAPAPO/DM_MATERIAL_GET_PEGID'
/SAPAPO/OM_PEG_CAT_GET_ORDERS - To get data from LC at matches the PEGID (= plant, material, storage location) and ATP-category - You will just have to specify the ATP-categories that match the MRP elements you would like to retrieve - LC doesn't store the names of the MRP elements
/SAPAPO/OM_ORDER_GET_DATA - Order details from liveCache - To retrieve all information of an order from LC that corresponds to an order id. You just have to use the field IS_GEN_PARAMS-SIMVERSION = '000' and fill the table IT_ORDER with your order id. If you only want to have the OUTPUT_FIXED indicator it would be faster if you use the FM I suggested and then only request ET_ORDKEY as an output table - this table contains the OUTPUT_FIXED indicator
/SAPAPO/DM_ORDKEY_SELECT_ORDNO GUID - of Order from liveCache - Need to provide Order No. and SIMID
/SAPAPO/RRP_HEURISTIC_GET_DATA - Heuristic details - EXPORTING iv_heur_id = heur_id iv_langu = sy-langu IMPORTING ev_heur_text = lv_heur_text EXCEPTIONS
heur_id_not_valid = 1 package_id_not_valid = 2 OTHERS = 3.
BAPI_PBSRVAPS_CHANGEKEYFIGVAL - To load a KF of planning book
BAPI_STSRVAPS_SAVEMULTI2 - To create stocks in SNP - Parameter for Version
/SAPAPO/RRP_LC_PEGID_GET_IO - Sales Order Fetch in APO - quantitiy, GUID and Pegging Area id but the sales order number
BAPI /SAPAPO/RRP_IO_COL - Additional Columns in Product View - RRP_USEX_COLS_GET_TEXT_01 method APPEND 'column1' to CT_COLS_TEXT.
APPEND 'Column2' to CT_COLS_TEXT
/SAPAPO/TS_DM_LOCK - User Change/Display Mode in Interactive Planning - Pass Values for GUI Id of Planning Area, Data Selection, Group By parameter
/SAPAPO/ADV_ALERT_SET - Generate Alert
/SAPAPO/MSDP_NOTE_WRITE - Write notes in SDP
Reports:
/SAPAPO/OM_DELETE_INCON_ORDERS - Delete inconsistent orders - Need to provide Order GUID
Useful TCodes:
/INCMD/UI Maintenance of Interchageable groups
/SAPAPO/86000118
/SAPAPO/AC03 Product Availability
/SAPAPO/AC04 ATP Simulation
/SAPAPO/AC05 Time Series
/SAPAPO/AC06 Temporary Quantity Assignments
/SAPAPO/AC07 Exclusive Lock Records
/SAPAPO/AC08 Generate Safety Stock Requirement
/SAPAPO/AC42 Display Product Allocation Situation
/SAPAPO/ADVM Macro Workbench
/SAPAPO/AHTS1 Start-up of Action Handler
/SAPAPO/AMON1 Alert Monitor
/SAPAPO/AMONMSG Settings 'Automatic Sending'
/SAPAPO/AMONMSG_SEND Sending Alerts
/SAPAPO/AMON_REORG Delete Database Alerts
/SAPAPO/AMON_SETTING Alert Monitor Settings
/SAPAPO/ATP2PPDS ATP -> PP/DS Conv. in Background
/SAPAPO/ATPC00 Global Settings
/SAPAPO/ATPC01 ATP Group
/SAPAPO/ATPC02 Business Event
/SAPAPO/ATPC03 Maintain Categories
/SAPAPO/ATPC04_05 Maintain ATP Check Control
/SAPAPO/ATPC06 Maintain Check Mode
/SAPAPO/ATPC07 Maintain Check Mode
/SAPAPO/ATPC08 Maintain Requirements Profile
/SAPAPO/ATPCH01 Maintain ATP Characteristic View
/SAPAPO/ATPCLOG_DEL ATP: Delete C Log Files
/SAPAPO/ATPCQ_AREA Maintain Plng Area Assignments
/SAPAPO/ATPCQ_CHECK Check Prod. Allocations Customizing
/SAPAPO/ATPCQ_CUBE Maintain InfoCube Assignment
/SAPAPO/ATPCQ_GENER Generate Objects
/SAPAPO/ATPCQ_GRP Maintain Product Allocation Group
/SAPAPO/ATPCQ_LST Maintain Seq. of Prod. Alloc.Proced.
/SAPAPO/ATPCQ_OBJ Maintain Product Allocations Object
/SAPAPO/ATPCQ_PRO Maintain Product Alloc. Procedure
/SAPAPO/ATPCQ_RESET Reset Time Stamp
/SAPAPO/ATPCQ_TSTMP APO: Generation Status, Transfer
/SAPAPO/ATPLOG Activate ATP Application Log
/SAPAPO/ATPLOG_DEL ATP: Delete Application Log
/SAPAPO/ATPLOG_DSP ATP: Display Application Log
/SAPAPO/ATPQ_ALERT APO: Product Allocations, Shortage
/SAPAPO/ATPQ_CHKCHAR Check Characteristics Combinations
/SAPAPO/ATPQ_CHKCUST Product Alloc. Assgmt, Sales Order
/SAPAPO/ATPQ_CHKUSG Check Product Allocation Assignment
/SAPAPO/ATPQ_COLLECT Generate Coll. Prod. Alloc. Charact.
/SAPAPO/ATPQ_KCGRP_U Product Allocations: Update Assgmt
/SAPAPO/ATPQ_PAREA_C Copy Characteristics Combinations
/SAPAPO/ATPQ_PAREA_K Copy Characteristics Combination
/SAPAPO/ATPQ_PAREA_R Product Allocations from Plan. Area
/SAPAPO/ATPQ_PAREA_W Product Allocations in Plan. Area
/SAPAPO/ATPTUBE_DISP Display Parameter Buffers
/SAPAPO/ATREE_DSP ATP: Display ATP Tree Structures
/SAPAPO/BLRG01 Generation of Reqmnts from Blocks
/SAPAPO/BOP ATP: Batch Backorder Processing
/SAPAPO/BOPI Backorder Processing (Interactive)
/SAPAPO/BOP_COMPARE Backorder Processing: Comparison
/SAPAPO/BOP_DELETE Delete Backorder Processing
/SAPAPO/BOP_MONITOR Monitor Backorder Processing
/SAPAPO/BOP_RESULT Backorder Processing Results
/SAPAPO/BOP_RUNTIME Backorder Processing: Runtimes
/SAPAPO/BOP_UPDATE Backorder Processing: Update
/SAPAPO/BOP_VS ATP: Backorder Processing for VS
/SAPAPO/BOP_WORKLIST ATP, BOP: Worklist
/SAPAPO/BP1 Send Transaction Data
/SAPAPO/BP2 Delete Transaction Data
/SAPAPO/C3 Display Application Log
/SAPAPO/C4 Maintenance of global parameters
/SAPAPO/C41 Activate/Deactivate Login
/SAPAPO/C5 Send Planning Results to OLTP
/SAPAPO/C6 Delete Application Log
/SAPAPO/C7 Find Entries
/SAPAPO/CALENDAR Calendar
/SAPAPO/CC Core Interface Cockpit
/SAPAPO/CCR CIF_DELTAREPORT3
/SAPAPO/CCRR CIF Compare/Reconcile Reorganization
/SAPAPO/CDPS0 DPS Variable View
/SAPAPO/CDPS1 DPS View 1
/SAPAPO/CDPS2 DPS View 2
/SAPAPO/CDPS3 DPS View 3
/SAPAPO/CDPSB0 Production Planning Run
/SAPAPO/CDPSB1 Prod. Planning Run in the Background
/SAPAPO/CDPSC6 Customizing: Setup Group Maintenance
/SAPAPO/CDPSC7 Maintenance of Setup Matrices
/SAPAPO/CDPSS0 Simulation Version
/SAPAPO/CDPS_REPT Evaluations
/SAPAPO/CDPS_SETUP List Output for Setup Matrix
/SAPAPO/CLPIPCAL Collaborative Promotion Planning
/SAPAPO/CLPISDP Collab. Supply and Demand Planning
/SAPAPO/CLPITPL Collaborative Transport. Planning
/SAPAPO/CLPRPDEL CLP: Delete RFQs
/SAPAPO/CLPRPIN Incoming RFQ Processes
/SAPAPO/CLPRPOUT Outgoing RFQ Processes
/SAPAPO/CLPRPSTART CLP: Publish RFQs
/SAPAPO/CLP_PBPULL Read Time Series
/SAPAPO/CLP_PBPUSH Send Time Series
/SAPAPO/CLP_SETTINGS Collaboration Partners
/SAPAPO/CMDS_DEFCNF Maintain Default Confirm. Profiles
/SAPAPO/CMDS_DEFCNTR Maintain Default Control Profiles
/SAPAPO/CMDS_DEL Delete Releases and Confirmations
/SAPAPO/CMDS_SCO1 Maintain Sales Scheduling Agreements
/SAPAPO/CMDS_SCO2 Delete Sales Scheduling Agreements
/SAPAPO/CMDS_SCO4 Manage Fiscal Year
/SAPAPO/CMDS_STPD Define Sold-To Party Determination
/SAPAPO/CMDS_STPSR Define Inbound Release Processing
/SAPAPO/COMP_VARIANT Comparison of Product Variants
/SAPAPO/CONSCHK Model Consistency Check
/SAPAPO/CONSPRF Model Consistency Check: Profile
/SAPAPO/CONSSHOW Read log from database
/SAPAPO/CPP CIF Postprocessing
/SAPAPO/CPP1 CIF Postprocessing: Multiple Call
/SAPAPO/CPP2 Display CIF Postprocessing Records
/SAPAPO/CPPA CIF Error Handling: Alert
/SAPAPO/CPPR Reorg. CIF Postprocessing Records
/SAPAPO/CQ SCM Queue Manager
/SAPAPO/CQINW qRFC Monitoring for Inbound Queues
/SAPAPO/CSNP Costs Maintenance: SNP
/SAPAPO/CSPRF Maintain TSP Profile
/SAPAPO/CTM Capable-to-Match: Main Screen
/SAPAPO/CTM01 CTM: Consistency Check
/SAPAPO/CTM02 CTM: Stock Limits
/SAPAPO/CTM10 CTM: Distribute Receipt Objects
/SAPAPO/CTMAPLOG CTM Logs
/SAPAPO/CTMB Execute CTM in Background
/SAPAPO/CTMCUST CTM: Global Customizing
/SAPAPO/CTMMSEL Selection of CTM Master Data
/SAPAPO/CTMORDSEL CTM: Maintain Order Selection
/SAPAPO/CTMSCPR Profile Maint. Supply Categorization
/SAPAPO/CTMSSTRAT Define CTM Search Strategy
/SAPAPO/CTMTP Transport CTM Profile
/SAPAPO/CTMTSTR Define CTM Time Stream
/SAPAPO/CTMVIEWER CTM: Call Viewer
/SAPAPO/CTRP Costs Maintenance - Vehicle Sched.
/SAPAPO/CULL_RTO_DEL Delete Production Data Structure
/SAPAPO/CURTO_GEN_DP Generate DP PDS
/SAPAPO/CURTO_SIMU Display Production Data Structures
/SAPAPO/CW qRFC Monitoring
/SAPAPO/DFCT Maintain Distribution Function
/SAPAPO/DISPLAY_CONF Display of DelSched and Confirmation
/SAPAPO/DMP1 Display Consumption Situation
/SAPAPO/DMP2 Generate Planned Independent Reqmts
/SAPAPO/DM_PEGCHECK Consistency Check Pegging Areas
/SAPAPO/DPC3 Change Overview
/SAPAPO/DPLSPLIT Deployment Stk Transfer Prioritizatn
/SAPAPO/GEN_CHK_PDS Generate iPPE Check PDS
/SAPAPO/GEN_PDS Generation of iPPE PDS
/SAPAPO/INCMD_MODEL Model Assignment
/SAPAPO/IPM01 integrated profile management
/SAPAPO/LCOUT Release from SNP -> DP
/SAPAPO/LOC3 Master Data: Locations
/SAPAPO/LOCTZCALC Calculate transport zone coordinates
/SAPAPO/LOC_CD_READ Change Documents for Location
/SAPAPO/LOC_DEL_LOG Location: Delete Application Log
/SAPAPO/LOC_DISP_LOG Location: Display Application Log
/SAPAPO/MASSGEOCODE Location: Mass-Geocoding
/SAPAPO/MAT1 Product
/SAPAPO/MC62 Maintain Characteristic Values
/SAPAPO/MC77 Change Selection
/SAPAPO/MC7A Location Split
/SAPAPO/MC7B Product Split
/SAPAPO/MC8D Mass Processing: Create Planning
/SAPAPO/MC8E Mass Processing: Change Planning
/SAPAPO/MC8F Delete Planning Job
/SAPAPO/MC8G Schedule Mass Processing
/SAPAPO/MC8I Mass Processing: Check Planning
/SAPAPO/MC8J Copy Mass Processing Jobs
/SAPAPO/MC8K Logs
/SAPAPO/MC8S Transfer Profiles
/SAPAPO/MC8T Activity
/SAPAPO/MC8U Transfer Profile
/SAPAPO/MC8V Calculate Proportional Factors
/SAPAPO/MC90 Release to Supply Network Planning
/SAPAPO/MC96B Maintain Forecast Profile
/SAPAPO/MCPSELDEL Delete selections
/SAPAPO/MD74 Reorganization: Adapt Indep.Reqmts
/SAPAPO/MNTPROF01 Maintain Display Profile
/SAPAPO/MP31 Maintain Promotion Attribute Types
/SAPAPO/MP32 Maintain Cannibalization Group
/SAPAPO/MP33 Maintain Promotion Key Figures
/SAPAPO/MP34 Supply & Demand Planner: Init.Screen
/SAPAPO/MP40 Maintain Promotion Bases
/SAPAPO/MP41A Maintain Settings for Report
/SAPAPO/MP41B Promotion Reports
/SAPAPO/MP42 Promotion Management
/SAPAPO/MSDP_ADMIN S&DP Administration
/SAPAPO/MSDP_FCST1 Lifecycle Settings
/SAPAPO/MSDP_FCST2 Assign Forecast Profiles
/SAPAPO/MSDP_SB Safety Stock Calculation
/SAPAPO/MSP01 Maint. and Service Planning Board
/SAPAPO/MSP_CYCMAINT Cycle Maintenance
/SAPAPO/MSP_ESIM MSP Easy Simulation
/SAPAPO/MSP_MOBJ Maintenance of one Maint. Object
/SAPAPO/MSP_PERFPROF Maintenance of Performance Profile
/SAPAPO/MTL01 Maintenance Task List
/SAPAPO/MVM Model/Planning version
/SAPAPO/OM03 Test Program for liveCache and LCA
/SAPAPO/OM04 Display of Current LCA Version
/SAPAPO/OM11 Log
/SAPAPO/OM12 Delete Log
/SAPAPO/OM13 Analyze liveCache and LCA Objects
/SAPAPO/OM16 Data Viewer
/SAPAPO/OM17 Data Reconciliation
/SAPAPO/OM25 Daily Reorganization of APO
/SAPAPO/OO_PPM_CONV Maint. Mode Comb. for PPM Conversion
/SAPAPO/OPT03 Optimizer User Display
/SAPAPO/OPT09 Optimization Version Display
/SAPAPO/OPT11 Log display
/SAPAPO/OPT12 Opt. server process overview
/SAPAPO/OPT_PRIOPROF SNP Opt.: Priority Profile
/SAPAPO/OPT_STOP Terminate Optimization Runs
/SAPAPO/PCMT Production Campaign
/SAPAPO/PDSLOG Log of PDS Generation
/SAPAPO/PEG1 Pegging Overview
/SAPAPO/PMON Plan Monitor
/SAPAPO/PMONDEF Definition: Key figure schema
/SAPAPO/POM1 Planned Order Management
/SAPAPO/POV1 Product Overview Transaction
/SAPAPO/PPC1 Backflush Entry
/SAPAPO/PPC2 Display Backflush
/SAPAPO/PPE iPPE Workbench Professional
/SAPAPO/PPELUI iPPE Workbench Express
/SAPAPO/PPFSCO Output of Confirmations
/SAPAPO/PPL1 Production List
/SAPAPO/PPM_CONV Conversion of PP/DS PPMs to SNP PPMs
/SAPAPO/PPM_CONV_310 Report for Generating SNP PPMs
/SAPAPO/PPM_CONV_LOG Log of SNP-PPM generation
/SAPAPO/PPM_DEL Mass Deletion of Plans and PPMs
/SAPAPO/PPT1 Product Planning Table
/SAPAPO/PROD_CD_READ Change Documents for Produkt
/SAPAPO/PSTRUCONS Plng Obj. Struct. Consistency Check
/SAPAPO/PWBSCH1 Create SA Release(s)
/SAPAPO/PWBSCH2 Release Output
/SAPAPO/PWBSCH3 Process Sched. Agreement Releases
/SAPAPO/PWBSCH4 Enter Confirmation
/SAPAPO/PWBSRC1 Ext. Procure. Rltnshps Maintenance
/SAPAPO/PWBSRC2 Delete External Proc. Relationships
/SAPAPO/RBA04 Integrated Rule Maintenance
/SAPAPO/RBAC01 Maintain Rule Strategy Determination
/SAPAPO/RELHSHOW Hierarchy Maintenance
/SAPAPO/REL_TO_OLTP Direct Release InfoProvider to R/3
/SAPAPO/REL_TO_SNP Direct Release InfoProvider to SNP
/SAPAPO/REORG_WUL Reorg. of Where-Used-Lists in LC
/SAPAPO/RES01 Change Resources
/SAPAPO/RET2 Restrictions Maint.- Create & Change
/SAPAPO/RET_EVAL Restriction Evaluation
/SAPAPO/RET_RP Restrictions & Reservation Planning
/SAPAPO/RLCDEL Delete Orders from Livecache
/SAPAPO/RLGCOPY Realignment
/SAPAPO/RRP1 Requirements View
/SAPAPO/RRP2 Process Order
/SAPAPO/RRP3 Product View
/SAPAPO/RRP4 Receipts view
/SAPAPO/RRP7 Mass Conversion of Orders
/SAPAPO/RRP8 ATP Check for REM Planned Orders
/SAPAPO/RRPEVAL Log for Last Planning Run
/SAPAPO/RRPLOG1 Display Logs
/SAPAPO/RRPLOG2 Delete Logs
/SAPAPO/RRP_ATP2PPDS ATP Tree Structure Conversion
/SAPAPO/RRP_NETCH Planning File Entries
/SAPAPO/RRP_SNP2PPDS Conversion SNP -> PP/DS
/SAPAPO/RSP_CONSIS Cons. Check RSC + Per.-Slot Creation
/SAPAPO/RSP_DBORSHOW Display Configuration for Orders
/SAPAPO/RSP_DCR Releasing Daily Packages
/SAPAPO/RSP_DICP Daily Package Creation
/SAPAPO/RSP_D_DEL Delete Delta Records
/SAPAPO/RSP_EXPLAIN Explanation Facility
/SAPAPO/RSP_G1 Planning Table
/SAPAPO/RSP_INFO Information Center RP
/SAPAPO/RSP_LC01 Initialize Time Series
/SAPAPO/RSP_LC03 Update Time Series
/SAPAPO/RSP_LC04 Restore Time Series
/SAPAPO/RSP_MCSC Manuf.Compl. Proposed Orders f.Stock
/SAPAPO/RSP_P1 Copy Orders
/SAPAPO/RSP_P2 Start Medium-Term Planning
/SAPAPO/RSP_P3 Reset Result of Medium-term Planning
/SAPAPO/RSP_RD_SIMU Simulation of Restriction Explosion
/SAPAPO/RSP_RSC Rescheduling
/SAPAPO/RTO_ORD_COMP Compare PP/DS PDS (R/3)
/SAPAPO/SCC02 Supply Chain Cockpit
/SAPAPO/SCC03 PPM Maintenance
/SAPAPO/SCC07 Supply Chain Engineer
/SAPAPO/SCC_TL1 Transportation Lanes
/SAPAPO/SCC_TL2 Mass Creation of Transport Rltnships
/SAPAPO/SCC_TQ1 Quota Arrangements
/SAPAPO/SCC_USR_PROF SCC Cockpit User Settings
/SAPAPO/SCE_USR_PROF SCC Engineer User Settings
/SAPAPO/SCHED_TEST Simul. Transp. & Shipment Scheduling
/SAPAPO/SDP8B Define Planning Book
/SAPAPO/SDP94 Supply & Demand Planner: Init.Screen
/SAPAPO/SDPALPR Assign Planners to Alert Profiles
/SAPAPO/SDPPLBK Assign User to Planning Book
/SAPAPO/SDPT SD Sched. Agrmt. Prod.Planning Table
/SAPAPO/SDPUSET SDP User Settings
/SAPAPO/SDRQCR21 Correction Report /sapapo/sdrqcr21
/SAPAPO/SEQ1 Interactive Sequencing
/SAPAPO/SEQ2 Model Mix Planning Run
/SAPAPO/SNP01 SNP Run
/SAPAPO/SNP02 Deployment
/SAPAPO/SNP03 Call Deployment Optimizer
/SAPAPO/SNP04 Transport Load Builder
/SAPAPO/SNP05 Capacity leveling
/SAPAPO/SNP06 Hierarchical Planning Disaggregation
/SAPAPO/SNP103 Maintain TLB Profile
/SAPAPO/SNP113 SNP: Maintain Costs
/SAPAPO/SNP2PPDS SNP -> PP/DS Conv. in Background
/SAPAPO/SNP94 SNP: Interactive Planning
/SAPAPO/SNPAPLOG Application Logs
/SAPAPO/SNPDRP DRP: Interactive Planning
/SAPAPO/SNPFCST Release SNP Forecast
/SAPAPO/SNPLLC Low-Level Code Determination
/SAPAPO/SNPOP Call Up SNP Optimizer
/SAPAPO/SNPOPLOG SNP Optimizer Log Data
/SAPAPO/SNPSA Sched. Agreemt: Interactive Planning
/SAPAPO/SNPSOP SOP: Interactive Planning
/SAPAPO/SNPSRC Call: Sourcing of Forecast in SNP
/SAPAPO/SNPTLB TLB: Interactive Planning
/SAPAPO/SNPVMI SNP: Interactive Planning with VMI
/SAPAPO/SUPCAT CTM Supply Category Maintenance
/SAPAPO/TI01 Evaluation of Production Tracking
/SAPAPO/TLBPRF TLB Profile Maintenance
/SAPAPO/TR30 Maintain DP/SNP Time Buckets Profile
/SAPAPO/TR32 Periodicities for Planning Area
/SAPAPO/TR_CD_QUOTA Change Docs for Quota Arrangements
/SAPAPO/TR_CD_TLANE Change Docs for Transportation Lanes
/SAPAPO/TR_DELTRPR Deletion of Prod.-Spec. Trnsp. Lane
/SAPAPO/TR_IGS_BPSEL Scheduling of GIS Preselection
/SAPAPO/TR_IGS_BUTRM Update of GIS Data
/SAPAPO/TR_IGS_RPSEL Reorganization of GIS Preselection
/SAPAPO/TSCONS Time Ser. Network Consistency Check
/SAPAPO/TSCOPY Copy/Version Management
/SAPAPO/TSCUBE Load Planning Area Version
/SAPAPO/TSKEYFMAIN Mass Maint. for Time Series Key Fig.
/SAPAPO/TSLCREORG Check LC Time Series Master Data
/SAPAPO/TSPSTRU Toolbox for Planning Object Struct.
/SAPAPO/TTC1 Schedule Maintenance
/SAPAPO/TTV1 Maintain Validity Area
/SAPAPO/TTW1 Itinerary Maintenance
/SAPAPO/VERCOP Copy Version
/SAPAPO/VERDELLD Delete a planning version
/SAPAPO/VERMER Merge Planning Versions (SNP)
/SAPAPO/VERMRM Merge Versions: Messages
/SAPAPO/VS01 VS Interactive Planning
/SAPAPO/VS05 Schedule optimization run
/SAPAPO/VS10 Transportation Service Provider Sel.
/SAPAPO/VS11 TPVS: Define Delivery/Pickup Windows
/SAPAPO/VS12 TP/VS: Define Compatibilities
/SAPAPO/VS50 Orders for Delivery Generation
/SAPAPO/VS501 Schedule Delivery Generation
/SAPAPO/VS51 Change Plan. Shipments to Shipments
/SAPAPO/VS511 Transfer Planned Shipments to OLTP
/SAPAPO/VS52 Check Release of Planned Shipments
/SAPAPO/VS521 Check Release of Planned Shipments
/SAPAPO/VS53 Deleting deliveries
/SAPAPO/VS531 Delete Deliveries
/SAPAPO/VS54 Deleting Shipments
/SAPAPO/VS541 Delete Shipments
/SAPAPO/VS551 Release Shipments in the Background
/SAPAPO/VS60 Monitor for OLTP Publication
/SAPAPO/VS70 Apply Split Rules
/SAPAPO/VS71 Determine Split Rules
/SAPAPO/VS72 Maintain Access Sequence for Splits
/SAPAPO/VS73 Maintain Split Rules
/SAPAPO/VSHIST Display the Change History
/SAPCND/AO01 Conditions: V_T681F for O RB
/SAPCND/AO03 Create condition table
/SAPCND/AO04 Change condition table
/SAPCND/AO05 Display condition table
/SAPCND/AO06 Condition Type: Rules-Based ATP
/SAPCND/AO07 Access: Maintain (Rules-Based ATP)
/SAPCND/AO08 Conditions: Procedure for O RB
/SAPCND/AO11 Create Rule Determination
/SAPCND/AO12 Change Rule Determination
/SAPCND/AO13 Display Rule Determination
/SAPCND/AO14 Copy Rule Determination
/SAPCND/AU11 Create Scheduling Step
/SAPCND/AU12 Change Scheduling Step
/SAPCND/AU13 Display Scheduling Step
/SAPCND/AU14 Copy Scheduling Step
/SCMB/ODM_CHECK ODM: Check Customizing
/SCMB/ODM_DATA_CHECK ODM: Check Data Consistency
AHTGL01 Action and Parameter Maintenance
AHTGL02 Definition of Action Points
BAPI BAPI Explorer
CL02 Classes
CL20N Object Assignments
CL22N Assign Class to Superior Classes
CL24N Class Assignments
CT04 Characteristics
LC10 liveCache Assistant
LSMW Legacy System Migration Workbench
MASSD Mass Maintenance
MDEM Orders with Explosion Errors
MDMD Matrix for Product/Location
MDRPM Control Data for RPM Products
OPPE13 User Assgmt: iPPE WB Professional
OPPELUI02 User Assignment: iPPE WB Express
PPECHK iPPE Consistency Check (Prod. Vers.)
PPEHDR01 Create a Production Version
PPEHDR02 Change a Production Version
PPEHDR03 Display a Production Version
RPMBAL Line Balancing for Demand Program
RPMCALL Explosion for RPM
RPMEVAL Evaluations
RPMLOG RPM Log
RPMPERF Display Performance Data
RPMPLF Planning Flags for Planning Matrices
RPM_DATEVECTORS_REOR Reorganize Table of Periods in LC
RPM_DATEVECTOR_COMPU Calculate Table of Periods f. Res.
RPM_OM_DATEVECTOR_SH Display Table of Periods from LC
RPM_RESOURCE_TSTREAM Display Resource Time Stream
RSKC Maintaining the Permittd Extra Chars
RSPC Process Chain Maintenance
RSSM Authorizations for Reporting
RZ20 CCMS Monitoring
SLG2 Application Log: Delete logs
SM37 Overview of job selection
SMQ1 qRFC Monitor (Outbound Queue)
SMQ2 qRFC Monitor (Inbound Queue)
S_AP5_28000002
S_AP8_94000074
S_AP8_94000284
S_AP9_75000079 IMG Activity: APO_PPS_CDPSC0
S_AP9_75000085 IMG Activity: APO_PPS_CDPSC8
S_AP9_75000086 IMG Activity: APO_PPS_CDPSC5
S_AP9_75000087 IMG Activity: APO_PPS_CDPSC4
S_AP9_75000088 IMG Activity: APO_PPS_CDPSC3
S_AP9_75000089 IMG Activity: APO_PPS_CDPSC2
S_AP9_75000090 IMG Activity: APO_PPS_CDPSC1
S_AP9_75000095 IMG Activity: APO_SNP_SNP112
S_AP9_75000101 IMG Activity: APO_SNP_SNP107
S_AP9_75000102 IMG Activity: APO_SNP_SNP105
S_AP9_75000130 IMG Activity: APO_ALLG_TRANS
S_AP9_75000138 IMG Activity: APO_ALLG_CAL
S_AP9_75000141 IMG Activity: APO_PPS_ROUNDPRF
S_AP9_75000142 IMG Activity: APO_DEMPL_BEDARF
S_AP9_75000146 IMG Activity: APO_DEMPL_WORK
S_AP9_75000169 Call the IMG Activity
S_AP9_75000183
S_AP9_75000184
S_AP9_75000202
S_AP9_75000203
S_AP9_75000206
S_AP9_75000212
S_AP9_75000249
S_AP9_86000053
S_AP9_86000062 IMG Activity: APO_SNP_SNP120
S_AP9_86000161
S_APO_12000024
S_APO_12000025
S_APO_12000026
S_APO_12000035
WUF Where-Used List
Tables:
Tables where SALES ORDER Data is stored in APO
In addition to the requirements in SAP liveCache, the SD order tables are also included in the comparison with SAP R/3. Data is stored in these tables that is required for SAP APO functions from the area of Global ATP, such as the check against product allocations and backorder processing.
Both the existence and the consistency of the stored data is checked, based on the most important fields, as well as on the connection between main item(s) and subitem(s) in the following tables:
· /sapapo/posmapn (mapping the item)
· /sapapo/ordadm_h (order header)
· /sapapo/ordadm_i (order item)
· /sapapo/schedlin (order schedule line)
· /sapapo/obref (object reference)
· /sapapo/sdfield (SD order/delivery: Item additional data, also called 'field catalog')
· /sapapo/ciflooku (CIF lookup table)
The following inconsistencies can arise:
· r3obj : R/3 object of item in table /sapapo/posmapn
· atpcat: ATP category of item in table /sapapo/ordadm_i
· chmod: Check mode of item in table /sapapo/ordadm_i
· pstyv: Item category of item in table /sapapo/ordadm_i
· from_time: Schedule line date in table /sapapo/schedlin
· to_time: Schedule line date in table /sapapo/schedlin
· uepos: Assignment of higher-level (main) item
(Mapping in table /sapapo/posmapn and entry table in /sapapo/sdfield)
· wmeng: Requested quantity in table /sapapo/schedlin
· edatu: Requested delivery date in table /sapapo/schedlin
· obref: Object reference between order and delivery item in table /sapapo/obref
· matnr (MainItem)/matnrMItem: Product of main item in table /sapapo/ordadm_i
· werks (MainItem)/werksMItem: Plant of main item in table /sapapo/ordadm_i
· lgort (MainItem)/lgortMItem: Storage location of main item in table /sapapo/ordadm_i
· Account assignment (MainItem)/accMItem: The account assignment of the main item, that is, the pegging area from table /sapapo/ordadm_i does not correspond to the account assignment in SAP R/3 (vbap-sobkz, vbap-vbeln and vbap-posnr)
Important Tables in R/3
Table Remarks
QTVB Product Allocation: Allocation used by Customer Order* Use this table to find allocation assignment by Sales Order
Important Tables in APO
Table Remarks
/SAPAPO/TBQTVB ATP: Parameter Buffer, Product Allocation Assignment
/SAPAPO/PAGZE001 PAG-Z001 Product Allocations: Characteristic Value* This table is generated when a Product Allocation Group is defined. Use it to convert the GUID into a CVC.
/SAPAPO/MATKEY Product Master* Use it to convert Material GUID into a material number.
/SAPAPO/MATLOC Location product Master* Use it to see valid material plant combinations (GUIDs) in APO.
/SAPAPO/MATMAP Mapping Table for Products* Use it to see mapping of material numbers in R/3, APO and GUID
/SAPAPO/LOC Locations* Use it to convert Location GUID into a Location number.
/SAPAPO/QTTAB Product Allocations: Schedule Line
/SAPAPO/SDQTVB SD Order: Product Allocation Assignment* Use it to see detailed allocation assignment by Sales Order
/SAPAPO/POSMAPN Order Items Mapping Table*Use to get GUID for Sales Orders
/sapapo/treqires- All the confirmed qty and confirmed timestamp for order transaction GUID
CDHDR, CDPOS- Broader- All changes
/sapapo/DMCP
R-Delete
N-Create
C-Change
Regards,
Naveen.

How to creates Aggrigates and Disaggragates in APO-DP

HI sap gures
this is suresh in APO-DP,how do you create the aggrigates and Disagrigates, if aggrigates
where it will be effected, please tell me.
Regards
suresh.

Hello Suresh,
Aggregation refers to the function whereby key figure values on detail level are automatically summed up at runtime and shown or planned on aggregated level. If, for example, you display the forecasted demand for a region in the interactive planning table, you see the forecasted demand that the system has summed up for the various distribution channels, product families, brands, and customers, for that particular region.
Disaggregation refers to the function that automatically provides the details of a key figure value from aggregrated level on detail level. If, for example, you forecast the demand for a particular region, the system breaks the value down immediately into the distribution channels, product families, brands, products, customers, and so on in this region.
Aggregation and disaggregation ensure a consistent planning approach throughout your organization. The sum of the values on detail level always equals the total on aggregated level. Key figure values are always saved on the lowest level of detail. If aggregates exist, the data is also saved on this aggregate level.
Regards
Rahul Chitte

APO DP disaggregation

Similar Messages

Maybe you are looking for