SAP Note 19231 - Transaction calls from MD04/05/06

Symptom:

Via the functions 'Display element' and 'Change element or 'Convert element', call transactions are made that are controlled via Table T457C from transactions MD04, MD05 and MD06.
The occurrence of errors is often because of incorrect entries in the table accessed.

1. You cannot branch from a shipping notification (confirmed purchase order items) to the corresponding purchase order or the scheduling agreement.

2. Processing purchase requisitions (endless loop) causes problems.

3. The SET/GET parameter for branching to the Sales and Distribution scheduling agreement, quotation or request for a quotation is wrong (for example, the number of the scheduling agreement is not supplied).

4. When branching to dependent reservations, the system does not start with the corresponding item but with item overview.

5. When branching to schedule lines in purchasing, the number of the scheduling agreement is not transferred.

6. Either you cannot branch from a release order for a contract or for a purchase requisition to the purchase order or the purchase requisition or system does not branch into the correct item.

7. Branching from free-of-charge deliveries to display or change does not function.

8. Branching from a 'scheduling agreement of an external service agent' to the display or change mode does not function.
Error message 61111: 'Selected function cannot be used for the element' is generated.

Cause and prerequisites

1. 2. 3. 5. 6. 7. 8. - wrong entries in table T457C.
1. 4. - not programmed

Solution

1.
--
In table T457C, include or change entries for shipping notification. You do this using Transaction SM31.

The complete new entries in the standard system are as follows:

TGrp: MD01 MD01
MRP elemnt: LA LA
Status: A V
TCode: -initial- -initial-
Processing routing: CALL_LIEFERAVIS CALL_LIEFERAVIS
Additional data: -initial- -initial-

You must also include the new FORM routine 'CALL_LIEFERAVIS' in Include LM61RF95. This FORM routine is contained in the standard system as of Release 2.2I or 3.0E.
Warning: One source code line is different in Releases 3.0D onwards from the source code in Release 2.2 and 3.0! This is indicated in the source code below. Make sure you only implement the relevant lines for your particular release.
LM61RF95:
---------
...
...
*---------------------------------------------------------------------*
* Transaktionscall: Lieferavis Anzeigen / Ändern *
* New in 2.2I (or 3.0E) *
*---------------------------------------------------------------------*
FORM CALL_LIEFERAVIS.
*--> Lieferavis ?!
CHECK MDPS-DELKZ EQ LAVIS.
*--> Nachlesen Positionsdaten
PERFORM SELECT_EKPO USING MDPS-DELNR MDPS-DELPS.
CHECK SY-SUBRC EQ 0.
*--> 5-Stellige Positionsnummer --> Eine Stelle nach links
MDPS-DELPS = MDPS-DELPS * 10.
*--> Avis zum Lieferplan
IF EKPO-BSTYP EQ CHARL.
SET PARAMETER ID 'VRT' FIELD MDPS-DELNR.
SET PARAMETER ID 'BSP' FIELD MDPS-DELPS.
CASE T457C-SELKZ.
WHEN CHARA.
CALL TRANSACTION 'ME33' AND SKIP FIRST SCREEN. <-- to 3.0C
CALL TRANSACTION 'ME39' AND SKIP FIRST SCREEN. <-- from 3.0D
WHEN CHARV.
CALL TRANSACTION 'ME38' AND SKIP FIRST SCREEN.
ENDCASE.
*--> Avis zur Bestellung
ELSE.
SET PARAMETER ID 'BES' FIELD MDPS-DELNR.
SET PARAMETER ID 'BSP' FIELD MDPS-DELPS.
CASE T457C-SELKZ.
WHEN CHARA.
CALL TRANSACTION 'ME23' AND SKIP FIRST SCREEN.
WHEN CHARV.
CALL TRANSACTION 'ME22' AND SKIP FIRST SCREEN.
ENDCASE.
ENDIF.
ENDFORM.

2.
--
The entries MD01/BA/A and MD01/BA/V are to be extended using additional data by the values
Parameter ID: BAP
Field name: MDPS-DELPS.

After the change, the following fields are available:

MD01 BA A Initial screen

Parameter-ID BAN Field name MDPS-DELNR
Parameter-ID BAP Field name MDPS-DELPS
Parameter-ID Field name
Parameter-ID Field name
Parameter-ID Field name
Parameter-ID Field name


MD01 BA V Initial screen

Parameter-ID BAN Field name MDPS-DELNR
Parameter-ID BAP Field name MDPS-DELPS
Parameter-ID Field name
Parameter-ID Field name
Parameter-ID Field name
Parameter-ID Field name

3. --
It is to be placed in all the entries with the following transactions:

TCode Parameter ID Field name
----------------------------------------------------
VA12/13 AFN Mdps-Delnr
VA22/23 AGN Mdps-Delnr
VA32/33 LPN Mdps-Delnr

4.
--
In the source code of Include LM61RU03, you must insert the lines marked with "corr" (in the standard system as of Release 3.0).
LM61RU03
--------
...............
...............
*--> Positionsnummer durch Multiplikation anpassen
CASE MDPS-DELKZ.
*--> 5-stellige Banfpo --> 1 Stelle nach links
WHEN BSANF.
MDPS-DELPS = MDPS-DELPS * 10.
*--> 5-stellige Bestpo --> 1 Stelle nach links
WHEN BSEIN.
MDPS-DELPS = MDPS-DELPS * 10.
*--> 5-stellige Bestpo --> 1 Stelle nach links
WHEN LPEIN.
MDPS-DELPS = MDPS-DELPS * 10.
*--> 4-stellige Resbpo --> 2 Stellen nach links
WHEN MRBED.
MDPS-DELPS = MDPS-DELPS * 100.
*--> 4-stellige Resbpo --> 2 Stellen nach links "corr
WHEN ARBED. "corr
MDPS-DELPS = MDPS-DELPS * 100. "corr
*--> 4-stellige Resbpo --> 2 Stellen nach links
WHEN UMRES.
MDPS-DELPS = MDPS-DELPS * 100.
WHEN ULRES.
MDPS-DELPS = MDPS-DELPS * 100.
ENDCASE.
......................
......................

5.
--

You must update the following entries in T457C:
TGrp MRPElem Status TCode
--------------------------------------
MD01 LE A ME33 (up to and incl. Release 3.0C)
MD01 LE A ME39 (as of Release 3.0D)
MD01 LE V ME38


Enter the following under additional data:
Parameter ID Field name
---------------------------------
VRT Mdps-Delnr
BSP MDPS-DELPS

6. --

You must copy the following entries in table T457C using transaction SM31 (simply by overwriting):
From: To:
MD01 BE A MD01 U1 A
MD01 BE V MD01 U1 V
MD01 BA A MD01 U2 A
MD01 BA V MD01 U2 V
MS01 PA A MS01 U3 A

Here, you must note that entries MD01, BA ... are to be corrected according to 2).
For example, to copy the first entry correctly, you only have to overwrite the column 'BE' with 'U1' in entry 'MD01 BE A' in SM31. Thus, the BE entry remains and the U1 entry automatically receives the appropriate additional data.
Moreover, so that you can branch directly to each item, you must insert the lines marked "<--INSERT in Include LM61RU03. Two of the lines are only to be implemented in Release 3.0B.
This is implemented in the standard system as of Release 3.0C or 2.2J.
LM61RU03:
---------

FUNCTION CALL_TRANSACTION.
...
...
*--> Positionsnummer durch Multiplikation anpassen
CASE MDPS-DELKZ.
*--> 5-stellige Banfpo --> 1 Stelle nach links
WHEN BSANF.
MDPS-DELPS = MDPS-DELPS * 10.
WHEN UAABR. "<--INSERT
MDPS-DELPS = MDPS-DELPS * 10. "<--INSERT
*--> 5-stellige Bestpo --> 1 Stelle nach links
WHEN BSEIN.
MDPS-DELPS = MDPS-DELPS * 10.
WHEN UBABR. "<--INSERT
MDPS-DELPS = MDPS-DELPS * 10. "<--INSERT
*--> 5-stellige Bestpo --> 1 Stelle nach links
WHEN LPEIN.
MDPS-DELPS = MDPS-DELPS * 10.
WHEN ULABR. "<--INSERT (3.0B only)
MDPS-DELPS = MDPS-DELPS * 10. "<--INSERT (3.0B only)
*--> 4-stellige Resbpo --> 2 Stellen nach links
WHEN MRBED.
MDPS-DELPS = MDPS-DELPS * 100.
...
...

7. --

In table T457C the entries 'MD01 VC A' and 'MD01 VC V' are to be overwritten with 'MD01 VI A' or 'MD01 VI V' with transaction SM31, so that all four entries are exist in T457C.

8.
--
Create the following new entries in T457C using transaction SM31 (as of Release 3.0A):

TGrp MRPElem Status TCode
--------------------------------------
MD01 VF A VA33
MD01 VF V VA32


Enter the following under additional data:

Parameter ID Field name
---------------------------------------
LPN MDPS-DELNR
LPN MDPS-DELNR