S2L results can be easily changed using enhancements in FM JITOUT04_SET_ACTION_INTERN.
As well as creating enhancement to the class CL_APO_MANAGER_S2L.
Note, that S2L will call this FM for every Call Control group in the final Supply Segments.
Destinations (or logical systems) are fetched from db-tables CIF_IMAX and CIF_IMOD (integration models can be created-activated-viewed using CFM1-CFM4 transaction codes). The destination determined through numerous parameters: material number, supply area, shipping point and so on.
The determination FM’s are CIF_IMOD_DESTINATIONS_RPM and CIF_IMODEL_CHECKACTIVEENTRIES (parameter IV_IMTYP type CIF_IMOD-IMTYP = T_RPM).
FM CIF_IMOD_DESTINATIONS_RPM fetches data from CIF_IMRPM, a table for RPM recipient determination.
Getting requirements from APO done via module S2L_APO_REQS_GET.
Reservation and dependent requirements are generated from table RESB into views V_S2L_RESB and V_S2L_RESB_NB (postprocessing records for production supply)
Component groups are splitting via FM JITOUT03_DETERMINE_COMP_GROUPS (e.g. modify outbound call action OMOD ‘FM JITOUT04_ACTION_MODIFY_JC’ corresponds and uses the same logic), depends on JIT call profile setting CPABPRF-PABZUS (‘Grouping by’ of summarized JIT calls, can be reached via “Define JIT call profile” tree in IMG):
eq 0: no aggregation
eq 1: summary by plant
eq 2: by plant and unloading point (jitodiaco_ls-ablad aka Storing Position)
eq 3: aggregation by plant, unloading point and supply area (jitodiaco_ls-prvbe):
TABLES: PPC_HEAD
P.S. To generate and reconcile runtime versions of active models you can use program RCIFIMAX.
#S2L015: No logical system found for material and plant
of8MGuxyKawb{xr5ixKg6m