Custom Fields Dropped

[Former Member]

Hi All,

We use classic model where SRM post PR in R3. (which later get converted to PO)

We recently upgraded from SRM 4.0 SP 6 to SP 13.

After the ugprade in our non prod system we found that custom fields that were posted from SRM to R3 are getting dropped.

Any hints or notes that debug/fix above issue?

Thanks

Nikhil

[dean_hinson2 · Accepted solution]

Hello,

Since these are custom fields, you had to have implemented a BADI to map those to the back-end system. Did you check the BADI? Is it active?

Regards, Dean.

[alison_lloyd]

We have recently applied sp13 and 14 and got the same issue (with all badi implemnetations deactivated) - did you solve the problem?

[Former Member]

Hi Alison

Yes we did fix the issue by making change to custom badi.

Looks like the data structure where custom field resided had changed

BADI Definition name BBP_CREATE_REQ_BACK (Create Requisition)

READ TABLE it_cuf_acc INTO ls_cuf_acc

• WITH KEY ref_value1 = req_items_wa-preq_item. <=== Before

WITH KEY ref_value2 = req_items_wa-preq_item. <=== After.

Let me know if this helps

BTW we only implemented SP 13 as it was released in April 2008 and we thought was stable rather than going for SP 14 that is relatively new. Can you comment on that? and any Note after SP 13 that is useful

Also we are currently looking at the following issue

1. Enter a country for partner ......... We did implement Note 702787....this only happens when we create a SC for a approved SC.

Thanks

Nikhil

Edited by: Nikhil on Feb 3, 2009 9:24 PM

Edited by: Nikhil on Feb 3, 2009 9:25 PM

[alison_lloyd]

Hi Nikhil,

Unfortunately this wasn't the issue. The problem is the customer fields missing from the front end (they do appear when running bbpsc01 in the backend) - this occurs even when all custom implementations of badis are deactivated.

FYI we did have a problem with the VAT calculation on the frontend (correctly calculated in the ERP system) which was corrected with note 1098595 (and the related correction for this) - manually implemented as not showing as valid for srm 4.0.

Kind Regards,

Alison