No backend PO in ECC5?

[Former Member]

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,

Mikey

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

[Former Member · Accepted solution]

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

BR

Dinesh

[former_member183819 · Accepted solution]

Hi

Please verify your BBPCO message type in WE02..as well as defined correctly in modelview BD64 ?

regards

Muthu

[Former Member · Accepted solution]

Hello Muthu,

I have message types ACC_Goods_Movement, MBGMCR and 3 other Y* bespoke message types that are not related to PO's. Will also including BBpco in addition to ACC_Goods_Movement, MBGMCR be sufficient in our Dist Model?

Thanks, Mike.

[former_member183819 · Accepted solution]

Hi

but you can try with BBPCO and try to get rid out of the problem.

BBPCO - PO Commitment posting

Add this message type too.and distribute to backend.In the meantime Please check your accounting configuration.

However you refer this thread on BBPCO.

regards

Muthu

Edited by: Muthuraman Govindasamy on Aug 27, 2008 9:58 AM

Edited by: Muthuraman Govindasamy on Aug 27, 2008 11:40 AM

[Former Member · Accepted solution]

Hi Muthu,

Thank you for the hint. I can now sucessfully get an outboubnd IDOC from our SRM system, however, the Inbound IDOC fails in R/3 with the message. Please can you elaborate what function module should be used for message type BBPCO01 as I am using Process Code 'BAPI' in R/3 transaction code WE20.

Thanking you,

M.

Function module not allowed: BAPI_IDOC_INPUT1

Message no. B1252

-

---

Diagnosis

The function module BAPI_IDOC_INPUT1 and the application object type which were determined are not valid for this IDoc.

Procedure

1. Please check that the process code in the inbound partner profile is correct.

2. If this is the case, you should check the ALE inbound methods ALE inbound methods for the process code and see whether the specified function module and application object type are correct.

3. If this is also the case, then the function module and the application object type are not permitted for the logical message type, message variant, message function and basis type that are contained in the IDoc control record. You should check whether the correct values have been assigned to these fields in the control record. If they do have the correct values, then the assignment to the function module and the application object type needs to be maintained.

-

---

[siowfong_chen · Accepted solution]

Hi Mike,

Can you check the settings in R/3?

Tcode: WE57

Look for function module: IDOC_INPUT_BBP_ACC_PO

The basic type is BBPCO01

Message type is BBPCO

Direction is Inbound and

Description is BBP: Commitment posting

Regards

SF

[Former Member · Accepted solution]

pl check the Yann's comment in thread given by Muthu

***********************************************************************************************************************************************************

You don't need BBPCO

As you said, the PO is replicated into the backend . Thus commitment is created.

The BBPCo is useful for standalone scenario where no PO is created in the backend thsu no commitment without this message type.

I am also using ECs with SRM50 and ECC60.

Kind regards,

Yann

***********************************************************************************************************************************************************

think the probing direction needs to be changed.

BR

Dinesh

[former_member183819 · Accepted solution]

Hi Mike

SF might be correct. Please check this note

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

Solution

Check and if necessary, correct the following entries:

1. Assign function module to message type

Transaction WE57

The following entries are required:

Module IDOC_INPUT_BBP_IV IDOC_INPUT_BBP_ACC_PO

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:

Inbound FM IDOC_INPUT_BBP_IV IDOC_INPUT_BBP_ACC_PO

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

IDOC_INPUT_BBP_IV (IDOC_INPUT_BBP_ACC_PO)

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'

regards

Muthu