Skip to Content
avatar image
Former Member

Plan Driven Procurement

Hi gurus,

i need some information about the Purchase Requisition (PR) state after the transfer of requirements from R/3 to SRM system.

1) which is the table to control the PR transfered in order to check if is possible to process in R/3 that purchase requisition? EPRTRANS or T160EX or others?

I hope EPRTRANS; but if i'm right, why the table is cleared after migration? In the other case (T160EX) the system (R/3) can check only PR transfereble and not transfered! Are there other tables?

2) What happen if i modify a PR in R/3 after its transfer to SRM?

3) What happen if i delete a PR in R/3 after its transfer to SRM?

Thank you in advance for your help.

Regards.

Simone

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Aug 08, 2006 at 05:39 PM

    Simone,

    The table that contains the purchase requisitions eligible for transfer from R/3 to SRM is EPRTRANS.

    Table T160EX defines which purchase requisitions in SAP R/3 will be populated in the EPRTRANS table by purchasing group and material group combination.

    When the requisitions are populated in EPRTRANS, they are replicated to the SRM Sourcing Cockpit as external requirements via the R/3 program BBP_EXTREQ_TRANSFER.

    -regards

    Shaz

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 10, 2006 at 02:28 AM

    Hi,

    New Requisitions have a copy status of 1 in the EPRTRANS table

    Changed Requisitions have a copy status of 2(changed,not transfered).

    New Requisiions and changes are transfered when the transfer program is run.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Yann Bouillut

      Simone,

      In planned procurement scenario, the criteria for requirements to be transferred from R/3 to sourcing cockpit is stored in table T160EX. Requirements that meet that criteria is flagged with an external profile (EBAN-EPROFILE = X) and logged in the EPRTRANS table. The EPRTRANS table entry is deleted once the requirement is transferred to the sourcing cockpit.

      The external profile flag on the requisition is what prevents the requisition from being ordered directly in R/3 and triggers the error message that you received.

      Kenny