Skip to Content
author's profile photo Former Member
Former Member

Sales Order Header texts

Hi All,

I am getting 3 texts from 850 IDOC on to Sales order header texts. I created 3 new textid's for them. This is working properly in Dev system and I moved them to Test system.

In Test system I checked the header texts, only the following text id's are comming. They do not have any data and remaining textid's are not comming.

DEV

-


Form Header

Header note 1

Header note 2

Shipping instructions EN

SAC code C000

SAC code I410

SAC code E740

Carrier requested by customer

PST EN

PED EN

ZTR EN

TEST

---

PST

PED

ZTR

I went to VOTXN and checked sales order header texts -> Textprocedure -> Z1-Order Text Procedure, Text Id's in this procedure, I see 11 ID's there in Dev and in test system I see only PST, PED and ZTR. I created these three in text object VBBK sales docu header. It is working fine in Dev and when I move these to Test system only these 3 id's are showing up. I wrote the code for this in ZXVEDU06. How come the remaining Id's are not showing here and values are not comming for these 3 Text Id's.

Can Someone please help me with this.

Thanks,

Veni.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jan 09, 2009 at 02:03 PM

    Sometimes the system can get a little "confused" with texts. I know this sounds strange, but SAP supplies program RVTEXTE to help clear things up in this area.

    There is an OSS note on it's use. Also make sure there's no user exit in MV45AFZA that's different between DEV and Test

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      FM IDOC_INPUT_ORDERS calls FM CREATE_TEXT from 2 subroutines CREATE_TEXT_HEADER

      (Include LVEDAF11) & CREATE_TEXT_ITEM (Include LVEDAF10).

      The name of the subroutines are self explanatory. CREATE_TEXT_HEADER creates header text and CREATE_TEXT_ITEM creates item text. Now depending on what TDID 0023 means for you ( I am not sure whether that is header text or item text) , you have to debug the relevant subroutine.

      FM CREATE_TEXT internally calls INIT_TEXT , SAVE_TEXT & COMMIT_TEXT in sequence. The error message TD607 is generated either from SAVE_TEXT or COMMIT_TEXT. Only debugging can determine the exact source.

      I would suggest put breakpoints on the mentioned subroutine calls and debug FM CREATE_TEXT to observe the sy-subrc values that are returned after SAVE_TEXT or COMMIT_TEXT call. Inside both these function modules, there is a subroutine perform save_text where exactly the sy-subrc is becoming not equal to 0. Try to understand the the root cause inside subrotune save_text.

      I have faced text updation issues earlier with EDI 862 (i.e. ORDCHG) which is almost similar to 850 (ORDERS).

      Based on your root cause, we may discuss possible solution.

      Edited by: Bhaskar Pal on Jan 16, 2009 2:00 AM

  • author's profile photo Former Member
    Former Member
    Posted on Jan 09, 2009 at 01:23 PM

    Regarding text ids missing in Test system:

    1) Check whether you have correctly assigned the right text procedure to the right item category.

    SPRO > SD > Sales > Sales documents > Sales document item > Define item category

    This is assuming that all assignments in VOTXN is correct.

    2) Recapture all missing texts in a new transport and retransport them to TEST system.

    Remember for Text ID configuration, some steps are client dependant and some are cross client components. This is important for your transport generation.

    Regarding values not coming from IDOC in the document:

    I am wondering why would you require implementing user exit ZXVEDU06 to populate text values from IDOC in the document? If you have configured the text IDs correctly, SAP standard will populate values automatically. You dont need any exit implementation.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.