You have the SES number and you really want to get the subtleties of administrations. Unpack the PACKNO of Service Entry Sheet.
T-Code: ML81N
Tables being referred to: Unpack the PACKNO of Service Entry Sheet
ESSR is the Help Passage Sheet Header Information. SES number and the PO number are accessible in this table.
ESLH is the Help Bundle Header Information. Kindly focus on the word Bundle Header Information. PACKNO is the essential key of this table.
ESLL is the Lines of Administration Bundle. This is bundle thing.
Interface between these tables are laid out utilizing PACKNO.
ESSR-PACKNO – > ESLH-FPACKNO (Parent bundle number). Check with utilitarian specialist assuming that field FPACKNO is to be utilized or HPACKNO is to be utilized for your framework.
ESLH-PACKNO – > ESLL-PACKNO
The last information in ESLL would have an additional one line for the Bundle Header recognizable proof. You want to eliminate this line in your rationale to get SES thing subtleties.
Choice 1. If ESLL-PACKNO = ESLL-FPACKNO .. Disregard this line.
Choice 2. Alternate way round is to erase the ESLL passage which has ESLL-Bundle = ABAP_TRUE (X).
Choice 3. Or on the other hand erase ESLL passage which has SUB_PACKNO NOT Equivalent to clear.
Kindly counsel your useful/business prior to carrying out choice 2 and choice 3. There may be some customization in your framework or different sub bundles which should be dealt with astutely. Choice I is the most secure wagered..
In one of our venture, we utilized choice 1.
If you would rather not hit two information base tables ESLH and ESLL, then straightforwardly get the information from standard data set view ML_ESLL (Administration Lines with Bundle Header Information), utilizing ML_ESLL-PACKNO = ESSR-PACKNO.
YOU MAY BE INTERESTED IN
Consistency and Extended Checks for Workflow Templates and Tasks
How to Trigger Class based workflows?
WhatsApp us