ATP in APO-Process

Hi All,
Can you please advise me regarding ATP in APO? what are the features that APO provides in ATP.
Thanks,
Vijesh

Hi vijesh.
Hope you are aware of Basic ATP checks in R/3. In APO along with the basic availability check (BAC) methods in R3 we have Advanced availability check (AAC) methods which are mentioned
below :
1) BOP (back order processing)
2) RBA (Rule based availability Check)
3)MLATP(Multilevel ATP)
4)CTP(capable to promise)
5)EDQA (event driven quantity assignment)
we can combine These BAC and AAC with the help of check instructions in APO.
if i keep writing it goes into pages... pls go through the below link which help you in understanding ATP in APO
Global Available-to-Promise (Global ATP) - SAP Library
Regards
Raja kiran R

Similar Messages

  • APO Process Order and Stock Transport Order

    Using APO Process and Stock Transport Orders are generated. Plant A generates the orders so that plant B can make and ship the product back to plant A against the stock transport order using VL10b.
    I see the stock transport order and process order in R/3. But when trying to ship the product to plant A, vl10b does not list any purchase orders?
    How do you associate a Process Order with a transport order?
    Something to do with the time horizons?

    I hope you have resolved this query at your end. In case yes, Please share your observations

  • GLOBAL ATP WITHOUT APO

    When I was at Sapphire in 2007, SAP demo'd a global ATP from within SD that utilized enhancement pack 1 or 2. Now I need to implement something like this, without using APO. However, I can't find any references to in through Enhancement Pack 3 (our current version). Has anyone seen this done? Basically, if a customer orders an item, then we want to check two distribution centers, then look at stores with either high avaialability/overstock or near-by. Thanks in advance for ideas. I just need leads not a detailed solution.

    Christophe
    The end objective of GATP is the same as that of regular ECC ATP - provide customers with committed dates and quantities. Having said that, GATP provides a HUUUGE improvement in functionality compared to the ECC ATP check - for example, rules based ATP check for product/ location substitution, multi-level ATP check, capable-to promise, etc.
    Because of these dramatic improvements in functionality, GATP has the potential to do a lot more than order promising - depending on the business requirement, it can reduce inventory, improve customer service, improve fill rates, ....
    GATP is executed in the APO system and is a module of APO. Best place to start with documentation is SAP help.
    Rishi Menon

  • ATP in APO

    How do I define in R/3 that availability check is done in APO?
    Best Regards
    -Italo

    You need to create ATP check interation model in R/3, ATP check will be done in APO for the material which are there in active integration model of ATP check.
    You can select the material in the ATP intergation model based on:
    Material
    Plnt
    Matl Type
    PlantSpec. Mtl Stat
    MRP Ctrlr
    MRP Type
    ABC Indicator
    or material selection based on TVARVC table variable.

  • HOW to delete old APO process chain logs.

    HI experts,
    Can anybody help me in gettting how to delete the old logs of APO daily delta process chain.
    Is there any standard job or any batch job for the same.
    Regards,
    yatindra

    Hi Yatindra,
    If you are using SCM 5.0, go to Tcode SE38 an run this program: RSPC_LOG_DELETE.
    In the screen you have to specify the date range from which you want to delete the logs.
    I hope this can help you.
    Regards.
    Marín.

  • SAP APO process

    Hi Team.
    Let me list down our entire demand planning process which we are currently doing and help me how we can improve the process in APO.
    Every starting of the ,sales sending us the sales order and forecast for next month and we are updating the same in our allocation file.
    Allocation file is summary of total demand and total supply.
    Demand from sales team and supply is the file from planners (planning also manual process, running BOM and getting the SF requirement)
    So the summary is :demand planning is manual..Planning is also almost manual .
    Please know how APO this process will be solved.
    Thanks for the help.
    Regards,
    Vijesh

    Vijesh,
    At a very high level:
    1.  The most common solution is that Sales Forecasts are entered in Demand Planning.
    2.  If ECC is used as the online transaction processing (OLTP) system, the Core interface (CIF) is activated. Regardless of what your OLTP is, Material numbers and Plants must be replicated in APO.
    3.  Master data for planning is replicated in APO (Bills of Material, Routings, production versions, purchase info records, Special procurement keys, etc etc)
    4.  Transactional data, such as Sales orders, FGs and SFGs stock, and FGs and SFGs supply orders are also replicated in APO.  It is possible to plan the entire BOM in APO, if such a solution is desired.
    5.  SNP and/or PP/DS are typically activated as planning engines.  Or, for a more complex, but higher quality solution, Capable to Match (CTM) or Optimizer can be used as planning engines, to create FEASIBLE plans.
    6. Finalized forecast is released to Planning.  This means the forecasts are copied from Demand Planning into the active area that is accessible to the planning engine.  Appropriate consumption of forecast is transparently done.  These released forecasts can optionally be replicated back to the OLTP.
    7. Planning is then run against the combined consumed forecast and sales demand.  Output of planning is generally planned orders and/or purchase requisitions.  These 'procurement proposals' can optionally be transparently sent back to the OLTP.
    In general, only planning is done in APO. Execution is generally not done in SCM, but is done within the OLTP.
    There are hundreds of variants of the above high-level overview.  I suggest that if you wish to pursue APO as a planning solution, you engage an external resource who can assist you to create a solution that meets all your business requirements, and can also help you through the implementation.
    Best Regards,
    DB49

  • Business Process: Final Demand Plan Key Figure in the past for APO DP

    Hello APO process experts,
    I have a BPX question for APO DP process owners, consultants or gurus:
    1.- Have you ever seen in any SAP APO customer, that in their APO DP planning books, they chose or designed to update the Final Demand Plan key Figure in the past closed historical buckets with the Actual Sales?
    Meaning that that in the Past closed historical Buckets, Actual Sales and Final Demand Plan, look exactily the same.
    Meaning that they create a dynamic Final Demand Plan key figure so to speak, yet they did not choose to create a key figure that also keeps the Final Demand Plan as originally entered.
    2.- Would you think that doing the above, without keeping any keyfigure in the planning book that actually shows what the Final Demand Plan was in the Past, is a good practice?
         The Demand Planner could still retreive the Final Demand Plan from BI reports, yet, dynamically they could never really see it in the planning book.
    3.- Do you think the above dynamic key figure would bias the Demand Planner's behaviour to manipulate the future open Final Demand Plan buckets to enter volumes in order sum to a monthly total, independently of what were the over and underachievements in the past (since they are not really visible to him) ?
    I would really like your feedback,
    thanks in advance!
    JD Loera

    Hello Thanks for your feedback.
    I agree with your point, and I hope that i still get more feedback from other Business Process Experts.
    I am trying to build a case for my client, to challenge the decision of their initial design as this practice is going to hurt the Demand Management process, if what they intend to achieve is a true "unconstrained demand plan"
    Much appreciated
    JD Loera

  • APO atp on sales orders with complete delivery.

    Hello all.
    We run ATP in APO for sales orders on a lot of products. Often a sales order will contain many different products & often Complete delivery will be chosen. When we do the ATP check one of the products may have a long delivery time compared to the rest of the products on the order, and since we have chosen complete delivery the delivery date for the entire order will be pushed back.
    Is there a way to find out which of the products in a given order causes the delay or do we have to have something coded you think?
    As is the users have to remove complete delivery and then do the ATP for each of the products to find out and that's expensive timewise.
    Any ideas welcome.
    Regards
    Simon Pedersen.

    Hi Simon,
    Is there any specific reason to choose "complete delivery" option. You can use delivery proposal option and this will provide delivery date to each schedule line as per material availability.
    In R3 go to SPRO->Sales and distribution->baisc function->Availability Check and Transfer of Requirements->Availability Check->Availability Check with ATP Logic or Against Planning->Define Default Settings In this transaction maintain availability check rule as "C"
    Regrds,
    Vaibhav

  • Routing ATP check (R/3 or APO) based on information on SO item (lgort)

    Hi All
    I have following question:
    I'd like to route ATP check to R/3 or to APO based on for example storage location. It means that for SL1 I want to get ATP check in R3 and for SL2 I want to get ATP from APO.
    Problem is that I haven't found appropriate user exit.
    In AVAILABILITY_CHECK_CONTROLLER->AVAILABILITY_CHECK if systems figures out that APO is active I'm always geting APO ATP. The necessary is that this can not be handled by CIF integration model setings. Please help.
    thanks a lot.
    jaro

    Hi,
    Try and see if this works.
    In the BADI CRM_DATAEXCHG_BADI and the method CRM_DATAEXCH_R3D_MBDOC_FILL (this method will trigger for the orders coming from R/3).
    Write the code to read the order using FM CRM_ORDER_READ and read all the item from this FM. Then set the status to "COMPLETE" for each of the items using the FM CRM_STATUS_CHANGE_FOR_ACTIV_OW .
    Please let me know how it goes?
    Thanks,
    KAruna.

  • ATP Check include in MRP and Exclude on Process order

    Dear all,
    We have a situation if we include reservations, deliveries and dependent requirements in ATP check in OPJJ, the system behaviour is that it includes all of them during MRP run. On process order level if we perform ATP check the system shows that all materials are available as it includes the dependent requirements and deliveries as well. we want to exclude dependent requirements and deliveries from ATP check on process order level so that it can only consider the quantities that are available in stock. and system will block the release of process order in case of short fall. as system includes dependent requirements and deliveries as well it always shows the msg that all material are available. Plz help and reply soon...... any suggestions or work arounds are always well come ..............

    Hi
    as i understand from ur question u dont want to considered dependent requrement and delivaries for
    this go to t code OPJJ and do not select dependent requrement and delivaries tick.
    after that go to t code OPJK and select material avalability as -03-No creation if material is missing
    hope this will help u
    regards
    sachin

  • APO GATP :  Unable to call APO during ATP check

    Question: While creating Sales order in ECC, ATP check in performed in ECC rather than in APO (GATP). Not sure where the issue is.
    1. RFC connectivity exisit between ECC and APO server -- Checked
    2. Integration model active with ATP flag checked and also ATP customization flag active 
    Note: The entries in  MARC table (field APOKZ)  for GATP relevant material shows a value of '3' .  I guess it should be either 1 or 2.   I am not sure what makes it a value of 1 or 2.
    Appreciate your help.

    Katrat,
    I will assume that you have never attempted ATP in APO on this ERP/SCM pair of systems.
    There are so many things that must be set up properly to first turn on ATP, the answer is not really suitable for a forum post.  I suggest you follow the Best Practices step by step.  When I have followed these steps, I have never been unsuccessful in establishing an initial ATP.
    [Connectivity|http://help.sap.com/bp_scmv250/BBLibrary/Documentation/B02_BB_ConfigGuide_EN_DE.doc] (you probably don't need this one, since you say you have already tested your connection successfully)
    [Replication|http://help.sap.com/bp_scmv250/BBLibrary/Documentation/B05_BB_ConfigGuide_EN_DE.doc]
    [Global ATP|http://help.sap.com/bp_scmv250/BBLibrary/Documentation/ATP_BB_ConfigGuide_EN_DE.doc]
    The above will get you to the point of a basic product check in SCM, with the option of RulesBasedAvailability check.  I suggest you ignore RBA until you have established a successful basic product check.
    Regards,
    DB49

  • How to make the ATP math work - receipts vs requirements

    Hello
    I have a 'qaundry'.   How can we make  receipts match requirments when we use ATP  [actually GATP -  from ECC  to SCM]. This to me to be a simple match problem that SAP  has not provided any config.  Even opening a message with them has not been helpful  and I am opening this message, as per their suggestion, on this forum.  Maybe someone out there has encountered this similar situation and can advise on how to handle this as a process +  customisation, perhaps ?
    We have two distinct processes that are primarily ATP based. [We use GATP / APO]
    Process # 1
    We use the Check Control :  ATP Group - CH
                                                  Business event - ZA - for sales orders
    In scope of check  we consider the following 'receipts'
                 Unrestricted Stock
                Blocked / Restricted stock
    under "Requirements"we have
    Sales Order - for restricted + Blocked stock 
    deliveries -     for restricted + Blocked stock 
    The match works fine in this scenario.
    In Process # 2  -  which is predominantly used, 
    We use the Check Control :   ATP Group - CH
                                                  Business event - A - for Orders
    we use the following "receipts"
             Unrestricted Use only [NO Blocked stk etc]
    For requirements
           sales orders - unrestricted stock only - this is what we  need.
           deliveries - unrestricted stock only - this is what we need.
    But because there is no subdivision available as with receipts  -  by default we also get the  requiremenmts from sales orders + delivery line items with  restricted / blocked stock .   This makes the match go haywire.
    So in process # 2 because we do not consider the receipts for blocked  stocks, the requirements from the blocked stock lines creates artificial shortages and we have issues where sales  orders do not confirm.  The scope of check considers only unrestricted stock but the requirements from restricted stock come in and deflate the ATP stock
    Is there a standard way we can net out the blocked / restricted  stock related sales  orders and deliveries requirement lines from the Check control that  does NOT consider blocked receipts ?
    Any help, suggestions, guidance in this would be greatly appreciated. 
    Rupendra K. Sharma

    Hi DB49
    The business scenario is as follows :
    We have separate sales order document type  where we want to process restricted / blocked stock only.   We use batch management -  so while creating the sales order,  we manually assign / enter the batch #  in blocked stock  status - to the line item.   (I use the "blocked /restricted" stock - to mean the same thing,as opposed to "unrestricted" stock.)
    Scope of check
    Receipts -   restricted / blocked (50)   +  unrestricted stock   (75)  =  125
    Requirements -  restricted / blocked (50)  +  unrestricted stock  (75) = 125
    We use a userexit to flip the 'A'  to a 'ZA'  when this order type is used.   ATP check is okay - as we want to look at the blocked/ restricted stock as well,  in addition to the normal unrestricted stock.  Math is okay here.
    This order type and then its deliveries generate the requirement as expected -  the same batch #s  / stock we assigned manually.  This requirement  is under a broad bucket of 'requirement'  and does not differentiate whether its restricted or unrestricted.   You  will notice that unlike 'requirements',   receipts can be clearly subdivided.
    However when we use the standard orders -  we want to stick to just unrestricted stock.   The 'A'  stays as is -  and we look at receipts ONLY in unrestricted stock.    However,  the requirements from the blocked stock sales orders and then its deliveries get pulled in - under the broad requirement of  -  Requirements.
    Under this process - Scope of check
    Receipts -   restricted / blocked (0)   +  unrestricted stock   (75)  =  75
    Requirements -  restricted / blocked (50)  +  unrestricted stock  (75) = 125
    Receipts <  Requirements by  50 -  so we have a shortage.
    Basically what we need to do for the second scenario is to filter out the requirements  for blocked / restricted stock.
    I do hope this helps explain the business process.
    Thanks
    Rupendra.

  • 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 (GUID’s) 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.

  • ATP Check for deliveries

    Hi Experts
    Can we perform check against deliveries in APO GATP?
    What are the prerequesites to perform ATP check against deliveries.
    In scope of check  we want to select production orders which are in released status.
    Please give your inputs.
    Regards

    Preetam,
    After creating the supporting configuration, APO ATP checking is thereafter 'turned on' by creating and activating an ATP integration model in the ERP.  Generally, it is done by material/plant combination.  Therefore, if you turn on ATP checking for Sales orders, you also turn it on for all other types of docs (including deliveries) for that particular material/plant combination.
    I hope you have thought out this whole process.  The main reason for using ATP checking in APO is that APO has a richer suite of ATP solutions.  If your business requirements are satisfied by the ATP checking in ERP, then it makes no sense to spend the money to implement ATP in APO. Your original issue had to do with making released production orders relevant for ATP for deliveries.  If this is the only new requirement, then this can easily be managed in ERP.  OVZ9>select your Availability check, with checking rule B (deliveries).  Under "incl production orders" select 'F'.  From a business perspective, this means that some of your deliveries will be created without stock on hand, and therefore will not be immediately shippable.  You need to make sure that this process change is integrated throughout your warehouses.
    And, to your final question.  If your delivery item category(s) are already relevant for ATP checking in ERP, they will also be relevant for ATP checking in APO.  Since deliveries do not use RBA, you do not have to worry about adding new ERP delivery item categories for the conversion to APO ATP checking.  Most commonly in APO, one uses only the 'product check' (similar to the standard ERP ATP check) for deliveries.
    Rgds,
    DB49

  • Unpegged Supply Records in ATP Enabled Plan

    OK this is a variation of a thread I had up about two weeks ago. Working an SR on this and seem to be spinning wheels a bit. We run two plans daily. One plan is for planner/buyers to launch planned orders and reschedules etc. We follow up with a second plan that points to ATP. The ATP plan has unpegged planned orders with an action = Release that do not respect any order modifers...whether it be FDS, FLM, Min order, Max order etc...etc... The analyst points to sales orders being entered and schedule while collections is running. His reasoning is because we are running enable 24 x 7 and he believes the records are being inserted via ATP Post Plan Processing. We are struggling with this for collections runs when we do not have OM or PC folks around. Thoughts? Thanks!

    'Origination Type' column will be shown in the supply/demand window(of the planners w/b) in the 'Order Tab' and will be displayed by default after 'order priority'.
    Possible values are 'Atp' & 'Planning'.
    Lookup-Type code Meaning
    MSC_ORIGINATION_TYPE 1 Planning
    2 Atp
    msc_orders_v selects the origination_type based on the record_source in msc_demands, msc_supplies & mfg_lookups.
    You can identify it via this way.

Maybe you are looking for