Skip to Content

Restrict PR flow to APO

Hi friends ,

We are using R/3 PR for different purposes .

I want to CIF over Purchase Requisition of some specific type only (Let say ZSTR of Stock transfer) . But in CFM1 there is no such filter option .

Only two information available with me to differentiate between PR is Document type and Creation Indicator .

Can you please guide me how can I restrict non relevant PR to be CIF over to APO as i donot want to see unnecessary PR in APO ?



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    May 21, 2008 at 08:33 AM

    APO does not know PR Document types. They are decided when the APO generated PRs come from APO to R3.

    There is a Stock Transfer Order Configuration in R3 which determines the 'Document Type' of a PO/STO

    between a Shipping and Receiving Plant. This one is mandatory apart from APO Setup for POs planned by

    APO to reach into R3 without resulting in a SYSFAIL Que.

    So APO knows no 'Order Types'.

    The APO PR/STOs sent to R3 use this config ...

    It is in R3 in SPRO->MM->Purchasing->Purchase Order->Setup STO->Assign Document Type One-Step Procedure.

    The Other Option is to Write a User-Exit in APO Inbound (for PR coming from R3 to APO) or R3 Inbound (for PR coming from APO to R3) to control the Type of PR. In R3->APO Integration Model generation there is No Control on PR document type.

    USER EXIT : APO Inbound

    Try SMOD APOCF024 or APOCF006 to see if we can Restrict the PR via a Document Type.

    APO Outbound : Try SMOD APOCF013.

    USER EXIT : R3 Inbound

    Try SMOD CIFPUR02.

    You will have to Code to Restrict the PR Document type ... especially from R3 to APO.

    Hope this helps. Reward Points if this does.


    Ambrish Mathur

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Ambarish,

      Where in APO we do this setup for PO's flowing from APO to r/3. I 've a problem where in we create STO in APO and send to R/3. But the STO is stuck in R/3 inbound with error, "please enter Vendor". I doubt system is assigning destination location as customer and asking vendor for source location, which should not happen in case of STO. where is this assignment happening? in R/3 or APO?


  • avatar image
    Former Member
    May 21, 2008 at 04:39 PM

    Yes and the problem is that CIF uses the same document type as ME21.

    So you have to use default settings for both manually created PO's and APO generated.

    Ken Snyder

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 26, 2008 at 07:38 AM

    Dear Nitesh

    Even i was working on similar issue and i was able to get some info from This has to be developed using user exit or a BADI. Pl find the below info for your requirement


    1. Change External Procurement Orders Before Writing to the liveCache

    You can use the BAdI /SAPAPO/DM_PO_CHANGE you can change the data of the purchase requisition, purchase order, confirmation, inbound delivery, schedule line and planned VMI sales order before it is saved to the liveCache

    User Exits

    Customer-specific CIF Enhancements for the Procurement Process (SAP APO and SAP R/3)

    1. SAP R/3 SAP APO

    · CIFPUR01 ( Enhancement for the Transmission of Customer-specific Purchase Order Fields ),

    To change purchasing data from purchase requisitions, purchase orders, scheduling agreement schedule lines (OLTP scheduling agreement) and confirmations/shipping notifications (for APO and OLTP scheduling agreements).

    EXIT_SAPLMEAP_001 Customer-Exit for Selection of Customer-specific Purchasing Data

    · CIFPUR01 ( Enhancement for the Transmission of Customer-specific Fields, Sources of Supply

    To control which data for scheduling agreements, contracts and purchasing info records are sent from the OLTP system to the SAP APO system.

    EXIT_SAPLCSRS_004 Customer-Exit for customer-specific selection of vendor/plant location

    Rewards Points if it helps



    Add comment
    10|10000 characters needed characters exceeded