Skip to Content
0
Mar 13, 2007 at 05:57 PM

When is customization dangerous even if the BADI's/exits are all there ????

74 Views

In this blog post here:

/people/david.halitsky/blog/2007/03/08/the-astrobiology-of-enterprise-soa-how-planet-abap-can-seed-life-on-planet-bpx

I gave a schematic outline of the badi's and exits required to customize SAP QM in a particular way.

Up until recently, it was thought that we only had to use these badi's and exits

to update QALS records in order to link an inspection lot to an inspection plan that is not the one that standard SAP logic picks.

But it turns out that we not only have to update QALS in this way, but also delete SAP-added records from AFFL, AFVC, AFVU, and AFVV and re-add our own corresponding to the operations in the non-standard plan we're selecting for the inspection lot.

OK - so we know exactly how to do these deletes and re-adds, because the way SAP does the original inserts into AFFL/AFVC/AFVU/AVFF (during a MIGO goods receipt post) is perfectly clear - the sequence of FMs and forms is:

FM's:

qeev_tables_generate

qpap_plan_read

qpap_post_qapo

co_bt_order_post_qm

co_vb_order_post

FORMs performed from co_vb_order_post:

affl post

afvg_post (takes care of afvc, afvv, afvu)

But even though we know what we're doing, and even though we can do everythign we need to do with an SAP-delivered BAdI or exit, maybe what we're doing is still too dangerous because we're relying on SAP keeping a number of different files interrelated in exactly the way they are now:

QALS

MAPL

PLKO

PLFL

PLAS

PLPO

AFVC

AFVV

AFVU

AFFL

What do you think ?

Thanks in advance for whatever time you can afford to spend considering this matter ...

djh