IMPORT_LOGFILE_KEY_TOO_SHORT
Hi,
in my z report i use FM 'L_TO_CREATE_DN'.
Sometimes i get this dump 'IMPORT_LOGFILE_KEY_TOO_SHORT'.
I´ve debugged the code and the dump arises within FM 'L_TO_CREATE_DN' in statement COMMIT WORK.
I´ve searched in OSS but i haven´t found anything conclusive.
Why is this happening?
Any hint or suggestion will be greatly appreciated.
Best regards.
Hi,
OSS Note 102103 solved my problem.
The key here is to find the correct FM´s that should be passed to the program taht must be run.
Best regards.
Similar Messages
-
Hi
Requirement is to copy the text from PO to Inbound delivery.Need how and what are all the step in configuration required?
-PrabuHi,
Solution
This note should help to map the text determination procedure from the
purchase order in the system correctly.
The function 'Text from purchase order' is available as of Support
Package SAPKH46B32 in Release 4.6B and SAPKH46C23 in Release 4.6C.
The following consultation refers to Customizing as of Release 4.70 and
higher - transaction VOTXN.
However, it is also relevant for Releases 4.6B and 4.6C as of the
Support Packages mentioned above - transaction VOTX.
Customizing for the procedure texts from purchase order -> delivery
1. Delivery type definition
Define your own delivery type for texts from purchase orders.
Since preceding documents from purchase order and sales order may
exist for deliveries, a separate delivery type is required for a
correct text determination.
Create access sequences
Example: instead of replenishment delivery RD -> new ZRD
2. Text determination procedure definition
Use transaction VOTXN (VOTX) and create your own text procedure at
header level as well as at item level.
3. Creating access sequences
For the new text determination procedures, use text objects EKKO and
EKPO to create new access sequences.
If you only want to find texts in this access sequence that were
created manually in the purchase order, text object EKKO or EKPO is
sufficient.
Here you should also maintain the condition for both text objects.
These are
EKKO > '1'
EKPO > '50'
The maintenance of additional text objects in these access sequences
is also possible of course, for example, 'TEXT'.
4. Text determination procedure assignment
Assign the new text determination procedure of the header texts to
the new delivery type and the text determination procedure of the
item texts to the relevant item categories.
In VOTXN (VOTX), this assignment is required.
Check in case of errors in the texts from purchase order procedure
1. Check: Customizing
> see above
2. Check: Table RVTXOBJ
If the system issues error message VC 220 'Only special text objects
are allowed' when you create the text objects EKKO and EKPO in
transaction VOTXN (VOTX),
check the table RVTXOBJ.
To do this, use transaction SE16 to go to the table.
If the entries EKKO and EKPO are missing there, execute the SDTXNMUP
correction report.
This reorganizes the table. -> For further information, see SAP Note
711954.
3. Check: Table TFRM
Use transaction SE16 to display the table contents of the TFRM table
and enter the 'TXNM' field value as the selection condition for the
group indicator for copying control (GRPZE).
Check if the entries for TXNM with grouping numbers (GRPNO) 018 and
019 exist > EKKO/EKPO.
> table TFRM
GRPZE GRPNO BEZEI
TXNM 001 VBBK text name
TXNM 002 VBBP text name
TXNM 003 MVKE text name
TXNM 004 TEXT text name
TXNM 005 VBKA text name
TXNM 006 KNVV text name
TXNM 007 KNVK text name
TXNM 008 KNB1 text name
TXNM 009 KNA1 text name
TXNM 010 MATERIAL text name
TXNM 011 KNMT text name
TXNM 012 VTTK text name
TXNM 013 VBBK text name
TXNM 014 VBBP text name
TXNM 015 KONA rebate payment
TXNM 016 WBRK text name
TXNM 017 WBRP text name
TXNM 018 EKKO text name <<<<<<<
TXNM 019 EKPO text name <<<<<<<
If these two entries are missing, use the solution provided in
Note 524453. The cross-client RV80INCTFRM report generates the
missing entries in TFRM.
Then start the RV80HGEN report that regenerates the relevant
includes.
You must take into account the comments in the long text of Note
524453.
Caution:
You should NOT implement the two entries manually in the FV46TNNN
include
Since this is a generated include, these entries would be lost
during the next generation (RV80HGEN).
Then you would no longer find texts from the purchase order.
Implement Note 524453 instead.
For information about the function of transaction VOFM, see also
Note 327220.
4. Error message VC 220
You receive the above error message with the text
IMPORT_LOGFILE_KEY_TOO_SHORT in the REFER_TEXT_AFTER_COMMIT function
module.
This means that an error occurred in the interface of the update
module during the local update.
To solve the problem, carry out the RSVBLOCL report for the
REFER_TEXT_AFTER_COMMIT function module.
The update module is then regenerated.
Check for a data transfer routine:
Some customers still use the workaround from Note 53593 and have defined
their own text determination routine in transaction VOFM.
As of Note 417883, this is no longer required, since the text
determination procedure from the purchase order is now supported and is
set as default.
5. Transaction ME2O - (Delivery to provision of materials for
subcontract order)
The text determination for deliveries from the provision of
materials for subcontract order is not possible in the standard
system.
- Sanjeev -
Dear friends
I have a scenario where i need to bring the master data text to inbound delivery text.what are the settings required.Is it possible?
Regards
AaryabalajiHi,
This note should help to map the text determination procedure from the
purchase order in the system correctly.
The function 'Text from purchase order' is available as of Support
Package SAPKH46B32 in Release 4.6B and SAPKH46C23 in Release 4.6C.
The following consultation refers to Customizing as of Release 4.70 and
higher - transaction VOTXN.
However, it is also relevant for Releases 4.6B and 4.6C as of the
Support Packages mentioned above - transaction VOTX.
Customizing for the procedure texts from purchase order -> delivery
1. Delivery type definition
Define your own delivery type for texts from purchase orders.
Since preceding documents from purchase order and sales order may
exist for deliveries, a separate delivery type is required for a
correct text determination.
Create access sequences
Example: instead of replenishment delivery RD -> new ZRD
2. Text determination procedure definition
Use transaction VOTXN (VOTX) and create your own text procedure at
header level as well as at item level.
3. Creating access sequences
For the new text determination procedures, use text objects EKKO and
EKPO to create new access sequences.
If you only want to find texts in this access sequence that were
created manually in the purchase order, text object EKKO or EKPO is
sufficient.
Here you should also maintain the condition for both text objects.
These are
EKKO > '1'
EKPO > '50'
The maintenance of additional text objects in these access sequences
is also possible of course, for example, 'TEXT'.
4. Text determination procedure assignment
Assign the new text determination procedure of the header texts to
the new delivery type and the text determination procedure of the
item texts to the relevant item categories.
In VOTXN (VOTX), this assignment is required.
Check in case of errors in the texts from purchase order procedure
1. Check: Customizing
see above
2. Check: Table RVTXOBJ
If the system issues error message VC 220 'Only special text objects
are allowed' when you create the text objects EKKO and EKPO in
transaction VOTXN (VOTX),
check the table RVTXOBJ.
To do this, use transaction SE16 to go to the table.
If the entries EKKO and EKPO are missing there, execute the SDTXNMUP
correction report.
This reorganizes the table. -> For further information, see SAP Note
711954.
3. Check: Table TFRM
Use transaction SE16 to display the table contents of the TFRM table
and enter the 'TXNM' field value as the selection condition for the
group indicator for copying control (GRPZE).
Check if the entries for TXNM with grouping numbers (GRPNO) 018 and
019 exist > EKKO/EKPO.
table TFRM
GRPZE GRPNO BEZEI
TXNM 001 VBBK text name
TXNM 002 VBBP text name
TXNM 003 MVKE text name
TXNM 004 TEXT text name
TXNM 005 VBKA text name
TXNM 006 KNVV text name
TXNM 007 KNVK text name
TXNM 008 KNB1 text name
TXNM 009 KNA1 text name
TXNM 010 MATERIAL text name
TXNM 011 KNMT text name
TXNM 012 VTTK text name
TXNM 013 VBBK text name
TXNM 014 VBBP text name
TXNM 015 KONA rebate payment
TXNM 016 WBRK text name
TXNM 017 WBRP text name
TXNM 018 EKKO text name <<<<<<<
TXNM 019 EKPO text name <<<<<<<
If these two entries are missing, use the solution provided in
Note 524453. The cross-client RV80INCTFRM report generates the
missing entries in TFRM.
Then start the RV80HGEN report that regenerates the relevant
includes.
You must take into account the comments in the long text of Note
524453.
Caution:
You should NOT implement the two entries manually in the FV46TNNN
include
Since this is a generated include, these entries would be lost
during the next generation (RV80HGEN).
Then you would no longer find texts from the purchase order.
Implement Note 524453 instead.
For information about the function of transaction VOFM, see also
Note 327220.
4. Error message VC 220
You receive the above error message with the text
IMPORT_LOGFILE_KEY_TOO_SHORT in the REFER_TEXT_AFTER_COMMIT function
module.
This means that an error occurred in the interface of the update
module during the local update.
To solve the problem, carry out the RSVBLOCL report for the
REFER_TEXT_AFTER_COMMIT function module.
The update module is then regenerated.
Check for a data transfer routine:
Some customers still use the workaround from Note 53593 and have defined
their own text determination routine in transaction VOFM.
As of Note 417883, this is no longer required, since the text
determination procedure from the purchase order is now supported and is
set as default.
5. Transaction ME2O - (Delivery to provision of materials for
subcontract order)
The text determination for deliveries from the provision of
materials for subcontract order is not possible in the standard
system.
Maybe you are looking for
-
Hi experts , Can anyone guide me for writing a driver program for ADOBE forms ( created using SFP transaction) . I have created the form but dont know how to run it using a driver program since i m new to SFP. Plz help me. Message was
-
How to delete duplicate contacts in icloud
How do you delete duplicate contacts in iCloud so that they will not appear on all of my devices (iPhone, iPad, MacBook)?
-
Help needed in XML Publisher rtf file
Hi, My RTF is like, In first Page I will get Customer details, after that in the same page I will get invoice details, You can find my RTF srtucture from fallowing. Customer Name Phone Number: Address Invoice_Number Inv_Date Inv
-
Can not hear audio for tv episode
I have iTunes 8.0 and it was working fine, but I bought a tv episode today and when I go to play it i can't hear any sound. I can hear my other tv shows but this one episode does not work. any ideas on to what could be the problem
-
BAPI for vendor invoice posting Moderator message : Read forum rules before posting. Thread locked. Edited by: Vinod Kumar on Jul 28, 2011 5:35 PM