Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
LE-TRM (Application Component) Task & Resource Management⤷
LESI (Package) LES - TRM Interface Package
IMG Activity
| ID | SIMG_LTRM_USEXIT003 | Change Request Dependencies Based on Group |
| Transaction Code | S_DTR_07000022 | IMG Activity: SIMG_LTRM_USEXIT003 |
| Created on | 20010208 | |
| Customizing Attributes | SIMG_LTRM_USEXIT003 | Change Request Dependencies Based on Group |
| Customizing Activity | SIMG_LTRM_USEXIT003 | Change Request Dependencies Based on Group |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | LTRM_GRP_RQST_CHANGE |
Use
As soon as you release a group in LES, LES transmits the data of this group to TRM. TRM uses the transmitted data to update the requests that have already been created for the single transfer orders belonging to this group. You can modify the created requests at this stage using this BAdI.
To change the request, the BAdI refers to the following data:
- TO headers of all TOs belonging to the group (IT_LTAK)
- TO items of all TOs belonging to the group (IT_LTAP)
- Request headers of all the requests that have been created at the time that the single TOs were created (IT_LRQSH_GRP)
- Request items of all the requests that have been created at the time that the single TOs were created (IT_LRQSI_GRP)
- Request dependencies for all requests that have been added using BAdI LTRM_TO_RQST_CHANGE (IT_LRQNT_GRP)
- Request header interface of the current group (IT_LIRQH)
- Request items interface of the current group (IT_LIRQI). It is always empty at this point in time, because LES cannot create superbundles on its own.
You can create additional request headers and items of the current group by returning ET_LIRQH, ET_LIRQI.
The use of this BAdI is restricted to inter-TO dependencies. You can use it to define dependencies between items from several different transfer orders belonging to one group (for example, to create a superbundle).
Example
You are working with wave picks in LES. The wave pick that you created in LES contains several deliveries/transfer orders. When you release this wave pick in LES, the system transmits the group data to TRM. You want TRM to bundle these deliveries/transfer orders together in such a way that picker A picks the items of deliveries 1 and 2 that are located in aisle A of your high-rack storage. Picker B is to pick the items of deliveries 1 and 2 that are located in aisle B of your high-rack storage. At the end of the picking process, all items of delivery 1 are to be consolidated in one box, and all items of delivery 2 are to be consolidated in another box.
Requirements
Standard settings
LES does not transmit any information to the request items (IT_LIRQI) table when the system creates the request. Thus this table is always empty, and you can use this BAdI to define your own headers and items.
Recommendation
Use only A- or S-messages within the BAdI.
We recommend including TYPE-POOL trmgc in your BAdI coding. All constants valid for TRM are set in this type pool. The coding becomes more transparent if you do not need to set the corresponding values.
For example, use trmgc_docty_request instead of value 05.
Activities
Further notes
The example code works as follows:
If the group description contains the pattern *TRM*SB* (where * is a wildcard), superbundles are built in such a way that every two bundles are combined together to form a superbundle. So if a group contains 5 bundles, bundles 1 and 2 form superbundle A, bundles 3 and 4 form superbundle B and bundle 5 forms superbundle C.
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20020125 |
| SAP Release Created in | 46C |
