Skip to Content
avatar image
Former Member

No backend PO in ECC5?

Hi Gurus,

Please can someone shed some light on the following error.

We have activated extended classic scen in srm 5.0, but our srm PO does not replicate over to ECC5 as a display only doc. The checks our basis team have undertaken are:

i. No idocs are visible in WE05

ii. errors are displayed in RZ20 say: (a) IDOC comms error: 'error sending IDoc to FI/CO backend for PO3xxxxxxxx, (b) Comm error checking account assignment for PO3xxxxxxxx in system

iii. the trans type and doc no's are consistent in srm.

iv. no entries in srm table REQREF

Any input would be appreciated

Thank you,


Edited by: Mike Pallister on Aug 26, 2008 10:07 PM

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Aug 27, 2008 at 03:42 AM

    hope you have defined the backend doc type and the internal PO no range in SRM and external PO no range in ECC have been mapped.

    as far as I know PO data is handovered to ECC in BAPI and not in IDOC



    Add comment
    10|10000 characters needed characters exceeded

    • Hi Mike

      SF might be correct. Please check this note

      Note 330401 - Process code does not exist f. BBPCO01, BBPIV01


      Check and if necessary, correct the following entries:

      1. Assign function module to message type

      Transaction WE57

      The following entries are required:


      Type F F

      Basic type BBPIV01 BBPCO01

      Msg type BBPIV BBPCO

      Direction 2 2

      Object type BBPBUS2081 (not for Release 3.1)

      Note that object type BBPBUS2081 is not defined in Release 3.1*. In

      this case, the 'Object type' entry remains empty.

      2. Characteristics of inbound function modules

      Transaction BD51

      The following entries are required:


      Input type 1 1

      03.09.2008 Page 2 of 3

      Note 330401 - Process code does not exist f. BBPCO01, BBPIV01

      Dialog allowed No No

      3. Create the missing process code with Transaction WE42 (change inbound

      process code). You can name the process code whatever you want. 'IV01'

      or 'CO01' are examples.

      The entry should look like this:

      Process code IV01 (CO01)

      Description BBPIV (BBPCO) inbound invoice

      Option ALE Processing with ALE service

      Processing Type Processing by function module

      Save the entry. You are then on the detail screen. Enter:

      Module (inbound)

      Function module


      Application object

      Object type

      BBPBUS2081 (- no entry -)

      4. Maintain the process code that has just been created in the partner

      profile for the logical system.

      Transaction WE20

      Partner type 'LS'