PR document type in the back end system

[Former Member]

Hi

We have a requirement where a PR should always be created against a shopping cart.

In SRM5.0 we have BAdI BBP_TARGET_OBJTYPE in which Backend document type is the changing parameter.

but in our current SRM4.0 we dont have this BAdI .We only have the BAdI BBP_TARGET_OBJECTS in our version.

Do you know any Badis where we can assign the backend document type?

Regards

[Former Member]

Hi

Yes you can use <b>BBP_TARGET_OBJECTS</b> BADI. This will solve the problem.

Incase this does not help, For the time being, de-activate all the Active Customer BADI Implementations (Name starting with y or z) using SE19 Transaction and then again repeat the process of shopping again. Then observe the standard SAP behaviour.

Do keep me posted.

Regards

- Atul

[Former Member]

Hi Atul,

I have activated the BAdI BBP_TARGET_OBJECTS and my coding in the BAdI is as the one below.

loop at item_data into wa_item.

WA_ITEM-DOC_TYPE = 'EC1'.

modify item_data from wa_item transporting DOC_TYPE.

endloop.

The backend doc. type is EC1.

In this case when I do shopping, in backend NB type PRs are created instead of EC1. Is there any other thing that needs to be done.

How to debug if this BAdI is working fine.

Regards

[Former Member]

Hi

Have you replicated the Same document type rom R/3 into the SRM system.

Are you using Extended Classic Scenario (ECS) ?

The solution proposed in this post won't work in your case:

Using the BADI BBP_TARGET_OBJECTS to determine the backend doc type will only allow you to determine the follow-on doc type for each SC item: RS or PR or PO.

With this BADI, you set 1, 2 or 3 in ITEM_DATA-OBJ_TO_GEN.

But it does not provide you with the choice of the R/3 doc type (PR01 or PR02) for each "follow-on" doc type (PR).

There is a BADI to change de backend Doc type or the backend doc number: BBP_SC_TRANSFER_BE Determine Number Ranges and Grouping in Backend Documents

You can, independent of the standard, use the method GROUP_RQ to create a separate grouping for purchase requisitions.

In the standard, the system creates only one purchase requisition in the backend for all purchase requisitions with the same backend document type . If the document types are different, the standard creates a separate purchase requisition for each document type.

So you can use this BADI and its method GROUP_RQ to group material items in one side, and service items on the other side.

<b>Please go through the link for more details -></b>

<u>

</u>

Do let me know.

Regards

- Atul

[Former Member]

HI Atul,

Will this BAdI work in SRM 5.0? I activated this BAdI in SRM 5.0 and checked but it is not working.

Do you have any idea?

Regards

[Former Member]

Hi

It should work fine. <b>Seems to be a bug in the system.</b>

<u>Please go through the follwoing SAP OSS Notes -></u>

Note 942052 - Default implementation for BADI BBP_TARGET_OBJTYPE

Note 953700 Customer fields are not mapped in BBP_TARGET_OBJECTS BADI

Note 703564 BBP_TARGET_OBJECTS and user-defined fields 02.11.2005

Note 786758 BADI BBP_TARGET_OBJECTS: ITEM_DATA-MATERIAL not filled

Note 615405 No customer-specific fields in BADI BBP_TARGET_OBJECTS

Note 604420 Composite SAP note SRM 3.0 SP1 group

Note 436288 EBP: BADIs do not run after transport

Note 620079 BADI BBP_TARGET_OBJECTS: Reference fields not filled

Do let me know.

Regards

- Atul