on 09-10-2015 2:10 PM
Dear DMS experts,
Currently our client has following requirement - Attach DIRs at header level of Purchase order (ME23N) & Purchase contract (ME33K).
Both these SAP objects have same master table EKKO.
I was following the steps mentioned in SAP note 1417841.
However while maintaining the configuration 'Maintain Key fields' I came across the problem.
In this key fields screen, I can not enter EKKO table entry twice, since column 'Table' is the primary key.
Has any one tried this scenario before, for both these purchasing objects?
Looking forward to your expert help!
BR
Tushar.
Hi,
Even you attach link EKKO table it cannot be viewed at header level, You need to enter the DIR number at item level only.
These tables are to link the Purchasing document number with DIR but not at header level, If you require to have at header level you may need to go for an development. WIth the below settings you can view the DIR at item level only.
Rgds,
Nayeem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nayeem,
Thanks for the reply, I had the same information earlier.
Nevertheless, we have to attach the DIRs to the header level of Purchase Order & Purchase Contract.
Before we do the ABAP development, it's required to do this configuration of 'Maintain Key Fields'.
And here we're stuck. Since we're not sure what values are to be used in this 'Maintain Key Fields' customizing.
Anyways, thanks for the response.
Cheers,
Tushar.
http://help.sap.com/saphelp_erp60_sp/helpdata/en/b2/c043a66fab11d1949500a0c92f024a/content.htm
Hi Nayeem,
The implementation of this functionality is combination of both customizing as well as ABAP development.
Help documentation link from SCN. But as I mentioned earlier, we're stuck in the first step of customizing.
Cheers,
Tushar
Hi Tushar,
I don't understand your problem. In the mentioned customizing table (by the way: it is TCLO) you can maintain the key fields of tables.
Therefore every table can be entered only once because there is only one primary key for a table. Please recognize that you can scroll to the right and enter additional key fields (as it is necessary for EKPO: EBELN/EBELP).
The column "Transaction Code" is used to have a destination where to go if you are in an document info record and navigate to a linked object (e. g. material).
Unfortunately there is a problem with tables that are used for multiple object types as EKKO.
But you could solve this by creating a custom transaction that takes the EKKO-EBELN number, checks the type of the object and then calls ME23N/ME33K depending on the type.
Regards,
Benedikt
Hi Tushar,
the transaction will only be used for navigation from DIR/object link tab to the matching EKKO transaction. No user will have to use this transaction. It is a simple report:
REPORT Z_CALL_EKKO_TRANS.
START-OF-SELECTION.
DATA: lv_ebeln type ekko-ebeln,
lv_bstyp TYPE ekko-bstyp.
get PARAMETER ID 'BES' field lv_ebeln.
SELECT SINGLE bstyp FROM ekko
INTO lv_bstyp
WHERE ebeln = lv_ebeln.
CASE lv_bstyp.
WHEN 'F'.
CALL TRANSACTION 'ME23N' AND SKIP FIRST SCREEN.
WHEN 'K'.
CALL TRANSACTION 'ME33K'AND SKIP FIRST SCREEN.
WHEN OTHERS.
MESSAGE 'Wrong EKKO-type' TYPE 'I'.
ENDCASE.
Regards,
Benedikt
Hi Benedikt,
Thanks for the codes. I've already asked our developer to do a test with it.
The other part of customizing 'Maitain Key fields' - Since EKKO can't be used more than once, can we use any other standard table which has EBELN as key field?
Ex - EKKN?
Any pointers in this regard?
Cheers
Tushar.
Hi Tushar,
I think using EKKN is possible, but it will be misleading because EKKN contains other data.
I would create a Z-table (maybe structure is enough) with field EBELN.
In any way you have to do following things:
Regards,
Benedikt
User | Count |
---|---|
85 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.