Interesting scenario- user facing error while deleting a sales order

Hello All,
I have one interesting scenario and want feedback from your side as soon as possible
Scenario-
One of my clients is facing a problem while deleting a sales order.
the sales order he is trying to delete is the old order created in 2007.
when i see the document flow the user has created the export order, then delivered it, invoiced and sent it to accounting, accounting document is also cleared. then he cancelled the invoice, reverse PGI and deleted the delivery. the status of the sales order system is showing is being processed. but please note in this case after reversing PGI and deleting a delivery the delivery document disappears from the document flow.
document flow looks like this
Order - 200004715                     Being processed
invoice- 700005310                    completed
accounting 700005311                 cleared
Cancel Invoice 700005315            completed
Accounting 700005316                 cleared
Now, in 2008 user is trying to delete the sales order but he is unable to do the same. system is giving him message "unable to delete sales order because of subsequent document 70005310 (which is invoice number)"
Can somebody please throw some light on this problem.
Thanks in advance.

Hi,
As fas as I know, this is standard system behaviour. The reason - you have done PGI (which has created a material document as well as accounting doc) and invoiced & reversed (which again has created accounting documents & rversal documents). All these documents are referencing the sales order.
If you delete sales order, sales order number gets deleted from VBAK /VBAP tables.
Hence, in relational data base scenario (meanin SAP in this context), deletion of sales order after creation of subsequent documents is not feasible.
Hope it clarifies the issue.
Regards
Murali

Similar Messages

WHILE DELETING A SALE ORDER GETTING A RUNTIME ERROR " Screen: Illegal message"

Hi Experts,
While deleting a sales order giving run time error. PFB runtime error details.
If you know any OSS message, please let m know. I tried, but there is no luck.
Short text
    Screen: Illegal message
What happened?
    The current screen processing action was terminated since a situation
    occurred where the application could not continue.
    This is probably due to an error in the ABAP program or in the current
    screen.
What can you do?
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator.
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
Error analysis
    The program attempted to issue a " " message during "Exit Command" processing.
    This is an illegal operation.
    The program was terminated.
    Screen name.............. "SAPMV45A"
    Screen number............ 4001
How to correct the error
    The program must be modified to correct the error.
    The modification must be made in "Exit Command" processing.
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
Source Code Extract
Line SourceCde
    1 *---------------------------------------------------------------------*
    2 *       FORM YVBEP_LESEN                                              *
    3 *---------------------------------------------------------------------*
    4 *       Lesen der Tabelle YVBEP (nicht sortiert)                      *
    5 *---------------------------------------------------------------------*
    6 FORM YVBEP_LESEN USING US_POSNR
    7                        US_ETENR
    8               CHANGING CH_TABIX.
    9
   10   YVBEP = SPACE.
   11   YVBEP-MANDT = VBAK-MANDT.
   12   YVBEP-VBELN = VBAK-VBELN.
   13   YVBEP-POSNR = US_POSNR.
   14   YVBEP-ETENR = US_ETENR.
   15   READ TABLE YVBEP.
   16   IF SY-SUBRC > 0.
   17     MESSAGE E506 WITH US_POSNR US_ETENR.
   18   ENDIF.
>>>>>   CH_TABIX = SY-TABIX.
   20
   21 ENDFORM.
Could you please help on this issue.
Thanks
Srinu

Hi Srinu,
it looks like you got the error message Schedule line &1 &2 is missing in table YVBEP while deleting the sales order.
It seems, that there are no SAP notes regarding this issue. Do you have this issue with all orders or with a single order?
If only a single order causes this issue, maybe something was wrong during an update.
If you get this error for many orders, then custom code (modification, enhancement, user exit in MV45AFZZ, ...) may be the reason for it.
If you have no custom code in module pool SAPMV45A, then contact SAP for this issue.
Regards,
Klaus

Error while creating the sales order with billing reference

hi alll
i am getting error while creating the sales order with billing reference.The line items are coming in grey.I am not able to change the items as well as the quantity field.Can u guide me
cheers
shalsa007........

Dear SAP SD 007
I can confidently tell that an enhancement or an user exit has been applied in your scenario
You have to check that
Normally when creating a sales order with respect or referring billing documents the qty will be in editable mode and it is standard problem
Your people has solved the standard problem by enhancement
Usually OR--LF-PGI----F2 (SAY THE QTY IS 25 UNITS)
Now you are creating returns order with reference to F2 in the return order type Re there is a standard issue that user can edit the qty to 30 from the original 25
To solve this only your people have used userexit
Line items and qty greyed out means definately there is some enhancement or user exit applied
You have to check that
Regards
Raja

Error while saving a Sales Order in the CRM Mobile Application

Hi,
I am facing issues while saving a Sales Order in the CRM Mobile Application. I am getting the error message "Value Field KvLangu is not valid (Error: 236 / 1102)".
I would be very grateful if somebody had faced this issue before and this way could help me with some information.
Best Regards,
Rogerio Prado.

Hi Rogerio,
You should put mobile sales related messages in the forum "CRM Mobile applications"
This error message is coming because the language table SMOT002 might be empty in your mobile client OR it does not have all the values which have been customized in the system.
You need to have subscription based on publication "customizing objects" assigned to your site.
Regards
Vivek

Error while saving the Sales Order

Hi experts,
i am getting a runtime error while saving a sales order stating: SAPSQL_EMPTY_TABNAME. It says the field T681-KOTAB could be empty. I would give in more inputs. Someone plz help.
Thanks.

I would expect that KOTN521 would be a Database table defined in the ABAP Dictionary that relates to the condition implemented in 521 for the usage specified in that record.
You should be able to go into the info system, SE84, and search under ABAP Dictionary / Database Tables to see what KOTN521 is.
Also, since the only Keys to T681 are KVEWE and KOTABNR, and there are two KOTABNR entries with a value of 521, then there must be two different usages (KVEWE) associated with that table.
If you see what they are, you can check to see what the usages represent. Based on a lookup, it appears that a usage of N is for Free Goods, A is for Pricing etc. In our system, we only have A entries.
What are the usages for the 521 entries? Do they relate to Free Goods/Pricing???
Does the table KOTN521 exist in the ABAP Dictionary?
Answering these questions may get you closer to the answer.
Can you compare the values in these entries to what you have in different SIDs?
Is this problem happening in Production, or is it still in a development or Quality Assurance client?
If it is still in development or Q, then it may be that a recent customization change was made.
Compare the entries across your systems, if possible.
Good luck
Brian

RunTime Error while saving a Sales Order

Hi All,
When i am saving a Sales Order, the system is throwing a Runtime Error.
The ABAP Code in the Runtime Error screen as follows.
          select * from (t681-kotab) appending table <cond_tab>
                 up to 1 rows
                 where kappl = se_kappl
                 and   kschl = se_kschl
                 and   datbi >= se_date
                 and   datab <= se_date
                 and   (coding_tab).
Till these days, there was no such error while saving a Sales Order.
How to resolve this issue?
Regards
Pavan

Hi,
The below piece of code is trying to get the contents of the table mentioned in T681-KOTAB.
select * from (t681-kotab) appending table <cond_tab>
up to 1 rows
where kappl = se_kappl
and kschl = se_kschl
and datbi >= se_date
and datab <= se_date
and (coding_tab).
The reason could be is someone has screwed up the entries in T681 table. Check that out.
Try to put a break point on this SELECT query and see what the value of T681-KOTAB holds before the SELECT query. Check whether such a table entry exists in DB.
Let me know if you are still stuck up.
If you can send me the ST22 dump of the run time error, i might be able to help you more on this.
Hope this helps.
Thanks,
Balaji

Material Listing Error while creating the sales order

Hi Guru's
I have mantained a material in the lisitng for A002 combiantion for SO/DC/Pric. ref. material
While creating the sales order is throwing an error as material is not listed so the transaction is not possible.
I have done the basic invetingation on the folowing aspects
1)checking the material in the listing
2)Validity periods
3)Material not blcoked
4)Mateial is extened for the respective sales org
Kindly help ASAP.
Thanks & Regards
Tarakaram

Dear SAP SD 007
I can confidently tell that an enhancement or an user exit has been applied in your scenario
You have to check that
Normally when creating a sales order with respect or referring billing documents the qty will be in editable mode and it is standard problem
Your people has solved the standard problem by enhancement
Usually OR--LF-PGI----F2 (SAY THE QTY IS 25 UNITS)
Now you are creating returns order with reference to F2 in the return order type Re there is a standard issue that user can edit the qty to 30 from the original 25
To solve this only your people have used userexit
Line items and qty greyed out means definately there is some enhancement or user exit applied
You have to check that
Regards
Raja

Error while Saving Service Sales order.

Hi..
Please help me for resolving below error..
While saving service sales order error is coming as-
Invalid account assignment category...
Detailed Error-
"Assign components to a/c assignment category & Account Assigmnet Category not defined.
In customisining a/c assgnment cate for ser & mainta order .In standard define the following values for the order category 30.A/c Asd type general F,
A/c *** type Project Q,A/c assigment type Sales Order E,Sales Doc Project D".
Awaiting for your inputs....
Thanks
Manoj Mahajan

Hi Manoj,
Account Key assigned to the pricing condition hasn't been configured completely.
Please check the appropriate account key and speak to your FI team.
Pl award me points if it is helpful.
Let me know if you need more details.
Thanks,
Ramesh

WHILE DELETING A SALE ORDER GETTING A RUNTIME ERROR

hi to all experts,
whenever i try to delete a particular sale order im getting a runtime error
stating that
Short text
    Screen: Illegal message
What happened?
    The current screen processing action was terminated since a situat
    occurred where the application could not continue.
    This is probably due to an error in the ABAP program or in the cur
    screen.
Error analysis
    The program attempted to issue a " " message during "Exit Command" processing.
    This is an illegal operation.
    The program was terminated.
    Screen name.............. "SAPMV45A"
    Screen number............ 4001
Trigger Location of Runtime Error
    Program                                 SAPMV45A
    Include                                 MV45AFZZ
    Row                                     370
    Module type                             (FORM)
    Module Name                             USEREXIT_SAVE_DOCUMENT
SourceCde
              message e001(zm) WITH text-335 ltab-kunnr text-334.
            else.
              if ktab-jkunnr <> ltab-kunnr.
                ktab-jkunnr = ltab-kunnr.
                jobsitecode = ltab-kunnr.
                CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
                EXPORTING
                  input = jobsitecode
                  IMPORTING
                  output = jobsitecode.
                SELECT SINGLE * FROM kna1 WHERE kunnr = jobsitecode.
                IF sy-subrc = 0.
                  ktab-jname1 = kna1-name1.
                  ktab-jstras = kna1-stras.
                ENDIF.
                chg_flg = 'X'.
              endif.
            endif.
          else.
            message e001(zm) WITH text-336.
* Validation for relationship between Sold-to Party and Ship-to Party
*          if ktab-ckunnr+0(4) NE ktab-jkunnr+0(4).
*            message e001(zm) WITH text-335 ktab-jkunnr text-337 ktab-ckunnr.
*          endif.
          custcode1 = ktab-ckunnr.
          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
            EXPORTING
              input = custcode1
            IMPORTING
              output = custcode1.
          jobsitecode1 = ktab-jkunnr.
          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
            EXPORTING
              input = jobsitecode1
            IMPORTING
              output = jobsitecode1.
          SELECT SINGLE * FROM knvp
          WHERE kunnr = custcode1
            AND vkorg = vbak-vkorg
            AND vtweg = vbak-vtweg
            AND spart = vbak-spart
            AND parvw = 'WE'
Error analysis
    The program attempted to issue a " " message during "Exit Command"
    This is an illegal operation.
    The program was terminated.
    Screen name.............. "SAPMV45A"
    Screen number............ 4001
Trigger Location of Runtime Error
    Program                                 SAPMV45A
    Include                                 MV45AFZZ
    Row                                     370
    Module type                             (FORM)
    Module Name                             USEREXIT_SAVE_DOCUMENT

Hi,
Seems there is some problem with the user exit USEREXIT_SAVE_DOCUMENT..
Put a breakpoint and see.
Regards,
Nagaraj

ERROR WHILE CREATING THE SALES ORDER

Hi,
When creating the sales order i am entering "mode of transport"in TSW details and while trying to save it im getting a message saying "Express document "update was terminated"" recieved from the author "Rahul". If i dont enter the TSW detail while creating i am able to save the order and later in change mode i can enter the mode of transport.
When i check the inbox, it says "definately cannot transfer message to node SMTP due to connection error".
This is hapenning for only one user.
What could be the problem?
Regards,
Rahul.

Hi Rahul,
I think you need to enter the mode of transport in external details where it will take for further processing. TSW is different process.
Thanks
Pravin

Run time error while creating a sales order by va01

hi ,
while i am creating a sales order a runtime error occurs as i fill entry for sole to party and then material and quantity and as i press enter. the run time error is:
error in current abap program "saplv61z" had to be terminated because it has come across the statement that unfortunately can not be executed.
kindly solve my problem.
thanks.

Hi Agrawal
As you are getting run-time error after entering the sold to party and material and the error is in SAPLV61Z ,
close the session for sometime and open again and then create sales order and then enter sold to party and material and then check wheather you are getting or not. If you are still facing the problem then take the help of the ABAP & BASIS consultant's.
Regards
Srinath

Product allocation error while creating a sales order

Hi Gurus,
My client is using the availability check against product allocation functionality in sales order.while I am creating the sales order and entering the material system is throwing the error message product allocation XXX is invalid,after pressing the enter button system has thrown another error "incorrect index structure for table XMVERF_POS/000010" and unable to save the order.
I have checked the material master and the product allocation is assigned in basic data 1 view,I have also checked the IMG settings it has maintained and assigned to infostructure.Please let me know is there any config settings are missing related to product allocation.
Regards,
hari challa.

Please check if storage location is populated for the material. Also may be this material is a non-stock material and not relevant for storage location check.. If you have any non-stock items in your order and if you are populating the storage location in the order automatically, then this happens. Please check your code and bypass the check for non stock items.
Hope this helps
Regards
Sai

Error while creating the sales order using Proxy

Hi Folks,
I am trying to create a Sales Order using Proxy via BAPI "BAPI_SALESORDER_CREATEFROMDAT2" :
and i got this type of standard error message
<Message>FB call: insufficient parameters</Message>
few days back only i used the same bapi for creating the Sales Order and did it successfully...using the same parameters
I don't have any clue about this type error .
Kindly guide .
Regards,

Hi Nikhil,
How refreshing the cache and restart the server will help ?
basically i am testing the scenario at R/3 end only by generating XML template in SPROXY.
My ECC 6.0 is on sp 12....I am not sure is it configuration related error or a bug ? as i have used the same code in ECC 6.0 with sp 09.
regards,

Error while CIF'fing Sales order to APO

While I tried to CIF a Sales order from R3 to APO, there is ablicked Q in SMQ1 which reads
"Too many parameters specified with perform" in the FM /SAPAPO/CIF_SL_DOC_INBOUND.
Any ideas on what mightbe causing this issue and how to resolve this issue ?
Thanks

Hi
In SMQ1 I had executed blocked Q (F6) and system shows an information at the bottom left hadn corner as "Function module does not exist or EXCEPTION raised"
Even deleting Q and Reciffing SO didnt work..Application log in CFG1 doesn't show any exceptions. As the Q is blocked, I didn't see any meesages in APO log.
R3 SMQ1 log is displayed as below.
Function Module                 Queue Name                Status
/SAPAPO/CIF_SL_DOC_INBOUND      CFLDERPCLNT020_3316       Too many parameters specified with PERFORM.
CFG1 extended Log for FM CIF_SL_DOC_INBOUND while Ciffing SO to APO
Parameter: IS_APOINF
O,
Table: IT_REQX Entries:                   4
No.,U,U,U,U,M,U,Purch.doc. ,Item ,Schd,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,
1   , ,X, ,X,N,X,0000057680 ,000010,0001,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X, ,
2   , ,X, ,X,N,X,0000057680 ,000010,0002,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X, ,
3   , ,X, ,X,N,X,0000057681 ,000010,0001,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X, ,
4   , ,X, ,X,N,X,0000057682 ,000020,0001,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X, ,
Table: IT_SDDOC Entries:                   3
No.,Pmnt,P,Matl No. ,Matl No.                                ,Matl Grou,Prod.Hier.        ,Ma,Ac,Re,Co,Val. Type ,Profit Ctr,Mat
1   ,DCLF, ,MATERIALXYZ ,                                        ,100   ,                  , , , , ,          ,Z001DU
2   ,DCLF, ,MATERIALXYZ ,                                        ,100   ,                  , , , , ,          ,Z001DU
3   ,DCLF, ,MATERIALXYZ ,                                        ,100   ,                  , , , , ,          ,Z001DU
Table: IT_ATPFIELD Entries:                  83
No.,Number      ,MRP it,Field    ,Char                                    ,
1   ,0000057680 ,000010,LTIMEZONE     ,EST                                     ,
2   ,0000057680 ,000010,LZONE     ,0000000001                              ,
3   ,0000057680 ,000010,UEBTK     ,X                                       ,
4   ,0000057680 ,000010,PRREG     ,AE                                      ,
5   ,0000057680 ,000010,QNTY     ,31.000                                  ,
6   ,0000057680 ,000010,RESMOD     ,X                                       ,
7   ,0000057680 ,000010,RESMOD_BATCH     ,B                                       ,
8   ,0000057680 ,000010,SCHED_BWLPROCESS     ,E                                       ,
9   ,0000057680 ,000010,EXT_MATNR     ,MATERIALXYZ                       ,
10 ,0000057680 ,000010,UNAME     ,USERV                                 ,
11 ,0000057680 ,000010,/LPRIO     ,01                                      ,
12 ,0000057680 ,000010,POSGUID     ,                                        ,
13 ,0000057680 ,000010,BOP_FLAG     ,N                                       ,
14 ,0000057680 ,000010,BOP_SUPPORT     ,Y                                       ,
15 ,0000057680 ,000010,LREGIO     ,NC                                      ,
16 ,0000057680 ,000010,/UEBTO     ,0.0                                     ,
17 ,0000057680 ,000010,/UNTTO     ,0.0                                     ,
18 ,0000057680 ,000010,APO_SD_GID_EXT0001GOISSUE_DATE,20081002195959                          ,
19 ,0000057680 ,000010,APO_SD_GID_EXT0002GOISSUE_DATE,20081010200000                          ,
20 ,0000057680 ,000010,APO_SD_WMENG0001     ,31                                      ,
21 ,0000057680 ,000010,BPROC     ,ZAP1                                    ,
22 ,0000057680 ,000010,/UEBTO     ,0.0                                     ,
23 ,0000057680 ,000010,LOGSYS     ,ERPCLNT020                              ,
24 ,0000057680 ,000010,LLAND     ,US                                      ,
25 ,0000057680 ,000010,LAND1     ,US                                      ,
26 ,0000057680 ,000010,KZAZU     ,X                                       ,
27 ,0000057680 ,000010,APO_SD_REQ_EXT0002RECEIVE_DATE,20081012140000                          ,
28 ,0000057680 ,000010,APO_SD_REQ_EXT0001RECEIVE_DATE,20081006040000                          ,
29 ,0000057680 ,000010,/UNTTO     ,0.0                                     ,
30 ,0000057681 ,000010,LZONE     ,0000000001                              ,
31 ,0000057681 ,000010,BOP_FLAG     ,N                                       ,
32 ,0000057681 ,000010,PRREG     ,A                                       ,
33 ,0000057681 ,000010,UEBTK     ,X                                       ,
34 ,0000057681 ,000010,SCHED_BWLPROCESS     ,A                                       ,
35 ,0000057681 ,000010,RESMOD_BATCH     ,B                                       ,
36 ,0000057681 ,000010,RESMOD     ,X                                       ,
37 ,0000057681 ,000010,QNTY     ,21.000                                  ,
38 ,0000057681 ,000010,BOP_SUPPORT     ,Y                                       ,
39 ,0000057681 ,000010,EXT_MATNR     ,MATERIALXYZ                       ,
40 ,0000057681 ,000010,UNAME     ,USERV                                 ,
41 ,0000057681 ,000010,POSGUID     ,                                        ,
42 ,0000057681 ,000010,/LPRIO     ,01                                      ,
43 ,0000057681 ,000010,LTIMEZONE     ,EST                                     ,
44 ,0000057681 ,000010,APO_SD_GID_EXT0001GOISSUE_DATE,20081014195959                          ,
45 ,0000057681 ,000010,APO_SD_WMENG0001     ,21                                      ,
46 ,0000057681 ,000010,/UNTTO     ,0.0                                     ,
47 ,0000057681 ,000010,/UEBTO     ,0.0                                     ,
48 ,0000057681 ,000010,BPROC     ,ZAP1                                    ,
49 ,0000057681 ,000010,APO_SD_REQ_EXT0001RECEIVE_DATE,20081015040000                          ,
50 ,0000057681 ,000010,/UNTTO     ,0.0                                     ,
51 ,0000057681 ,000010,LREGIO     ,NC                                      ,
52 ,0000057681 ,000010,LOGSYS     ,ERPCLNT020                              ,
53 ,0000057681 ,000010,LLAND     ,US                                      ,
54 ,0000057681 ,000010,LAND1     ,US                                      ,
55 ,0000057681 ,000010,KZAZU     ,X                                       ,
56 ,0000057681 ,000010,/UEBTO     ,0.0                                     ,
57 ,0000057682 ,000020,LZONE     ,0000000001                              ,
58 ,0000057682 ,000020,/LPRIO     ,01                                      ,
59 ,0000057682 ,000020,POSGUID     ,                                        ,
60 ,0000057682 ,000020,BOP_SUPPORT     ,Y                                       ,
61 ,0000057682 ,000020,BOP_FLAG     ,N                                       ,
62 ,0000057682 ,000020,PRREG     ,A                                       ,
63 ,0000057682 ,000020,QNTY     ,11.000                                  ,
64 ,0000057682 ,000020,UNAME     ,USERV                                 ,
65 ,0000057682 ,000020,UEBTK     ,X                                       ,
66 ,0000057682 ,000020,SCHED_BWLPROCESS     ,A                                       ,
67 ,0000057682 ,000020,RESMOD_BATCH     ,B                                       ,
68 ,0000057682 ,000020,RESMOD     ,X                                       ,
69 ,0000057682 ,000020,EXT_MATNR     ,MATERIALXYZ                       ,
70 ,0000057682 ,000020,LTIMEZONE     ,EST                                     ,
71 ,0000057682 ,000020,/UEBTO     ,0.0                                     ,
72 ,0000057682 ,000020,/UNTTO     ,0.0                                     ,
73 ,0000057682 ,000020,APO_SD_GID_EXT0001GOISSUE_DATE,20081007175230                          ,
74 ,0000057682 ,000020,APO_SD_WMENG0001     ,11                                      ,
75 ,0000057682 ,000020,BPROC     ,ZAP1                                    ,
76 ,0000057682 ,000020,APO_SD_REQ_EXT0001RECEIVE_DATE,20081006040000                          ,
77 ,0000057682 ,000020,/UNTTO     ,0.0                                     ,
78 ,0000057682 ,000020,/UEBTO     ,0.0                                     ,
79 ,0000057682 ,000020,KZAZU     ,X                                       ,
80 ,0000057682 ,000020,LAND1     ,US                                      ,
81 ,0000057682 ,000020,LLAND     ,US                                      ,
82 ,0000057682 ,000020,LOGSYS     ,ERPCLNT020                              ,
83 ,0000057682 ,000020,LREGIO     ,NC                                      ,
Table: IT_REQ Entries:                   4
No.,M,EinkBeleg   ,Positi,Eint,MatNr                     ,Werk                ,AT,Charge    ,V.be,Offen              ,Menge ,Pla
1   ,N,0000057680 ,000010,0001,MATERIALXYZ                      ,LOC10                ,BM,       ,    ,31.000
2   ,N,0000057680 ,000010,0002,MATERIALXYZ                      ,LOC10                ,BM,       ,    ,0.000
3   ,N,0000057681 ,000010,0001,MATERIALXYZ                      ,LOC10                ,BM,       ,    ,21.000
4   ,N,0000057682 ,000020,0001,MATERIALXYZ                      ,LOC10                ,BM,       ,    ,11.000
Table: IT_QUOT_VB Entries:                   0
No.,Number      ,MRP it,PlanObj no            ,TSTAMP             ,ConfirmQty       ,Uni,ConfirmQty      ,Item ind.
Table: IT_CCV Entries:                   0
No.,Table                         ,CharValObj                                   ,Class    ,Char.                         ,Valid
Table: IT_DOC Entries:                   3
No.,M,EinkBeleg   ,Positi,V,V.be,
1   ,C,0000057680 ,000010,C,TA ,
2   ,C,0000057681 ,000010,C,ZOR,
3   ,C,0000057682 ,000020,C,ZOR,
Table: IT_GID Entries:                   0
No.,Purch.doc. ,Item ,GUID                  ,
Table: IT_DOCX Entries:                   3
No.,M,Purch.doc. ,Item ,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,U,
1   ,C,0000057680 ,000010,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,
2   ,C,0000057681 ,000010,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,
3   ,C,0000057682 ,000020,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,
Table: IT_ENQUEUE_ARGS Entries:0
No.,Cli,Model     ,LogSystem ,APOAppl   ,Created on,Changed ,ObjectType,Segm,S,BlockN,Created by ,A,Lengt,Vector
Table: EXTENSIONOUT Entries:                   0
No.,Structure                     ,Data
Table: IT_DOC_TPDS Entries:                   0
No.,Purch.doc. ,Item ,Location            ,API ,Purc,Purch.doc. ,Item ,
Table: IT_DOC_CUS Entries:                   0
No.,Purch.doc. ,Item ,
Table: IT_REQ_CUS Entries:                   0
No.,Purch.doc. ,Item ,Schd,Date      ,
Table: IT_QUEUE_NAMES Entries:                   0
No.,Q Name                  ,Dest.           ,
Table: IT_SD_MON_ITM Entries:                   0
No.,M,Number      ,Item ,G,CustFacLoc          ,CusF,Location            ,Loc.,Re,RJ,NO,RE,HighLe,Numera,Denom.,Uni,Numera,Deno
Table: IT_SD_MON_SCH Entries:                   0
No.,M,Number      ,Item ,Schd,GI Dt/Time,UE,
TIA
Edited by: SCM_Func on Oct 6, 2008 7:19 PM

Error while creating a Sales Order

Hi ,
I have created a material master for a material Y-350 in my system.I have defined it for the Plant 1100 (Berlin), Sales Org 1020 , Distribution channel 22.When i try to create a sales order for a customer in Dusseldorf,Germanyy , i get an error saying "Material Y-350 is not defined for sales org 1020,distr.chann 22,language DE".It means that a short text with the appropriate language exists(a short text must be available in the language of either the customer or the sales organization).I had it maintained in English.From where do i go and maintain it in German ?Kindly let me know.Thanks.

Hi,
First check what's the sales area assigned to your customer in Dusseldorf,Germany. It has to be Sales Org 1020 , Distribution channel 22.
To check that go to XD02 & enter customer number there and press "Customer Sales Areas" button. There you can view all sales areas available for your customer. Check whether Sales Org 1020 , Distribution channel 22. exists there. If not, from XD01, you have to extend your customer for that sales area again.
If that's there, then check the language in Material Master.
What you have to do is, go to MM02, give the Material number and go in by selecting Basic Data view.
Once go in, select "Additional Data" button option from the top.
Under "Descriptions" tab, maintain language "DE", since customer is from Germany.
Now try & see.
Best regards,
Anupa

Interesting scenario- user facing error while deleting a sales order

Similar Messages

Maybe you are looking for