Sales Order header still booked when lines are already closed

Hello all,
Well, im having problems to close a couple of Sales Orders...the lines are already closed but the headers reminds as 'Booked'....I checked the Workflow and one of the SO shows me this error message:
Error Message ORA-00376: file 354 cannot be read at this time ORA-01110: data file 354: '+LIVE_DG/liveclrvenus2/datafile/undotbs1a.801.702318343' ORA-00376: file 354 cannot be read at this time ORA-01110: data file 354: '+LIVE_DG/liveclrvenus2/datafile/undotbs1a.801.702318343'
Error Stack Wf_Event.Dispatch(oracle.apps.wf.notification.send) Wf_Notification.SendSingle(SYSADMIN, OMERROR, OMERROR_MSG, 26-JAN-11, WF_ENGINE.CB) Wf_Notification.Send(SYSADMIN, OMERROR, OMERROR_MSG, 26-JAN-11, WF_ENGINE.CB) Wf_Engine_Util.Notification_Send(OMERROR, WF2835788, 143218, OMERROR:OMERROR_MSG) Wf_Standard.Notify(OMERROR, WF2835788, 143218, RUN) Wf_Engine_Util.Function_Call(WF_STANDARD.NOTIFY, OMERROR, WF2835788, 143218, RUN)
Anyone knows how to fix this......
Regards
Edited by: 843193 on Mar 11, 2011 2:59 PM

See docs "Close Sales Order Headers With No Associated Open Lines, Order Header Workflows Or Order Line Workflows [ID 397565.1]" and "Order Management Suite - Some Datafix Patches and Scripts [ID 398822.1]". They might help. I currently have an SR in on the same situation, although I do not get the same error message you get.
Hope this helps,
Dana-B
Edited by: user9971618 on May 2, 2011 12:21 PM
Edited by: Dana-B on May 2, 2011 12:22 PM

Similar Messages

Copying sales order header data into delivery line item

Hi
In copy control from sales order to delivery I want to copy value in sales order header to all the items in delivery, can I achieve this in the header level data transfer routine (Source sales document type to target delivery doc type i.e TVCPL-GRUAK) or I have to do the changes in item level data transfer routine (TVCPL-GRUAP)
The requirement is to copy a value from VBAK into LIPS during delivery creation
Thanks
Javed

Dear Javed,
Your requirement sounds interesting.
If possible can you explain the scenario where we have to transfer the header data form order to item data in delivery?
Also if you have found the solution, can you please update the same.
Thanks & Regards,
Hegal K Charles

How to cancel the sales order - header and line status are in Entered Stage

Dears,
I have some sales order to be cancelled in which the header and line status are in *"Entered"*. I am not able to cancel these sales order.
Also note that these orders are for maintenance service.Once i book these orders the lines will change to closed status.
So it is not possible to book and cancel the lines.
Kindly me to resolve this.

926530 wrote:
Boss,
If i do Action-->cancel on header, it just makes the qty to zero.But the header and line status still showing as entered.It will not cancel the order.
The problem for me is that these lines are coming in my monthly reports. This is what your question says...be more specific as what is your issue..which in turn is your problem
How to cancel the sales order - header and line status are in Entered Stage
Coming to your Action-->cancel...as far as i know ...the header status will change to canceled..
unless until you have some processing constraints in place...which is stopping you...
HTH
Mahendra

OM Sales Order Header should be Closed Immediately after Lines are closed

Hi,
OM Sales Order Header should be Closed Immediately after Lines are closed.
Could you tell me how to modify the header workflow, if anyone has done this...could you please share.
Thanks

Thanks Mano, it worked.
I have one question in workflow, let me create new thread.
Could you please check my other question at below.
OM Notable able to capture Approver Rejected comments from the Note field in WF
OM Notable able to capture Approver Rejected comments from the Note field in WF

After rejection, sales order is still displayed in VKM1

Hi,
We have a system here with several types of sales document and several item categories as well.
When saving sales order with line items created, I generally have no problem to give a reason for rejection if they were blocked for credit reason. When I go back to transaction VKM1-blocked SD documents, I do not see those orders as they were rejected.
Nevertheless, some of my sales orders with a specific item categories are still displayed in VKM1, although a reason for rejection was entered in the sales order.
Would anyone have any idea how I can remove those sales I would like not to display anymore in transaction VKM1?
Thanks,
Ronan

Hi Ronan,
Please check in below areas.
1. Reason for rejection is set at item or header level.
2. check setting for the same in SPRO->SD->Sales ->Sales doc item->Define reason for rejection.
thanks.

How the sales order header status update?

Hello,
In the sales order header "STATUS" tab is there, under this status tab we can find OBJECT status if we click that object status it shows the Object number,Object category,status profile and status with status no. on which bases this status will update in the sales order header?
my case is Status "10-xxxx" set automatically for some orders.
Could you plz let me know on which bases, the status will be updated in the sales order?
Regards|KS

Hi
SAPu2019S GENERAL STATUS MANAGEMENT FUNCTIONALITY
General Status Management replaced order status management functionality in recent SAP releases (4.6C). This discussion will address general status management, as this is how SAP allows user statuses for controlling objects in this and future releases.
General Status Management applies to internal orders, project definitions, WBS elements, production orders and many other objects in SAP. For the purposes of this discussion we will concentrate on status management for internal orders and WBS elements. A list of all objects relevant for status management will be made available upon request.
A status is an indicator that fulfills two functions. First, it informs you that a particular status has been reached. For example, an internal order has been created and released; a settlement rule has been entered; a particular business transaction has been executed, etc. Second, it influences the business transactions you can perform for a particular status. A status can allow a business transaction; allow a business transaction but issue a warning message; or prohibit a business transaction altogether. If a warning message is issued it is up to the user whether the business transaction is carried out or not.
Statuses can be used to control and communicate. Statuses can be used in reporting (show me a report of all internal orders with a status of TECO, or technically complete). Statuses can be used as selection criteria (select all internal orders with a status of CLSD, or closed). Statuses can communicate the state of an object (ready for archiving, not ready for settlement execution).
There are SAP standard delivered statuses that apply to all object types. These are known as SYSTEM STATUSES. CRTD, REL, SETC, TECO are examples of SAP standard system statuses. SAP standard system statuses cannot be removed from use. You cannot override the SAP system status with a user status. You cannot change the behavior of an SAP system status.
User statuses (or user defined statuses) exist in addition to SAP standard statuses. User statuses are intended to augment or refine SAP standard statuses, not replace them. There is no limitation to the number of user statuses that can be created. Both system and user statuses influence business transactions in the same way.
An object can have multiple statuses active at the same time. A plant maintenance order can have released, preliminarily costed, work order printed and confirmed statuses all at the same time. For SAP display purposes only one status can be displayed on the status line in master data screens, but it is possible to see all active statuses for an object at one time by drilling down into the master data screens.
A STATUS PROFILE, or user status profile, contains individual user statuses and the business transaction rules defined for those statuses. There is no limit to the number of user status profiles that can be maintained in SAP. A user status profile is assigned to an order type or a project profile in configuration. This user status profile is then defaulted into all objects that reference that order type or project profile. A users status profile can be overwritten (or deleted) in an individual object (via native master data screens), but only if a user status has yet to be activated for that particular object. Once a user status has been activated for that object the user status profile cannot be changed.
HOW STATUS MANAGEMENT WORKS
When an object (internal order, WBS element, production order) is created SAP assigns the system status CRTD. MIT automatically releases the order, so the system status REL is also activated. If there is a user status profile defined in the order type (or project profile) this is carried over into the internal order (or WBS element). If not, only the SAP system statuses will apply to this object.
When a user executes a business transaction for this object, SAP checks the user status to see if that business transaction can be executed without any additional influence from a user status, can be executed but with a warning message being issued, or cannot be executed at all. SAP also checks whether the business transaction sets or deletes any other user statuses within the user status profile.
A user status may also be maintained directly in the object master data. Accessing the master data screens allows a user to manually maintain user statuses. If necessary, an authorization code can be assigned to a user status to ensure that no unauthorized persons can change the status of an object. Once changed, the new user status is fully active and acts no differently than if a business transaction set the user status.
Status management and business transaction control only work with standard SAP transactions. Z transactions will not show up on the business transaction list for an object. The business transaction table is configurable, but SAP strongly recommends not changing that table. SAP directly updates that table via support packs and it is often impacted during upgrades.
Authorization codes / keys are available in user statuses. The authorization code is checked only when user statuses are being set manually, from within the objectu2019s master data screens. This ensures the user has the proper authorization to set that status for that particular object. However, it is important to understand that SAP sets a user status in reaction to a business transaction it does not perform an authorization check.

Why the Sales Order is still being processed?

Hi,
This process is done: Sales Order (RE - Return) --> Return Delivery (Goods receipt) --> Billing
Sold-to party wrongly entered in the Sales Order, so they wanted to close the Sales Order. They did Cancellation for Billing (VF11) and reversed the Goods receipt (VL09).
Also, Reason for Rejection is put in the line item (VA02). However, the status of the Sales Order is still Being Processed instead of Completed.
From the Data Flow, it states that order-related billing status is still open*. But the Billing documents and Accounting documents are Completed and Cleared respectively as seen from the Data Flow.
How to close this Sales Order?
Thanks.

Dear Friend,
If you want to close any particular order then go to order reason and give the reason and save it.
The system will automatically close the order and would show processed and in the due lists also it would not appear.
award points if helpful,
regards,
Amlan

WBS Element ( Billing element ) assignment at sales order header level

HI,
There is provision of assign WBS Element at sales order header as well as item level , If Project WBS Element is assigned for each line item delivery and stock updating is happening from the project, But WBSE will assign at sales order Header system will not allowing to create project delivery( moment type 601Q), and stock updation ftom project.
Please let me know how this will happen ,
Regards,
Gangi
Edited by: Gangi Reddy Botchu on Jul 7, 2008 4:50 PM

SPRO - SD - Billing - Billing Plan - the first 5 config nodes (Define Billing Plan types / Define Date descriptions / Assign Date categories / Maintain Date Proposals / Assign Billing Plan types to Sales Doc types) are applicable to you.
this is pretty tranparent for a reference.
What else is required?

Sales group not filled form sales order header in PGI accounting Document

Hi all,
we are creating a sales order . when sold to and ship to is entered the sales group at the header level is fetched from the customer master automatically.
Now after changing the sales group,different from customer master,the sales order got saved as usual with a warning mesaage 'sales group is diiferent from customer master'.
After doing PGI and billing , the sales group fetched in billing document is same as that of sales order header,but when good issue delievry document is displayed , in accounting document of the material document (ie. in FB03),the sales group in profit segment tab is getting filled from customer master.
Now the requirement is to fetch the sales group from sales order header instead of customer master.

hi
check your copy control settings and change if required

Sales Order Header Data. Texts

Hy All Experts.
I wnt to put Filed Sales Order Header data. i go to transaction va02. ->> disp Doc. header Deatils.
select Tab Texts. --> Notes .
I wnt to put a notes in a sales order report. so hw to identify. that field.
Please guide me above matter.
Thnks
Bhavesh Panchal.

Hi Bhavesh Panchal,
              Use read text function module and get data from header text for ur sales report.
get object, id, en from text area. Double click the text area and click Goto menu and choose header.
for ex
     TDNAME = IT_ORDER-VBELN.
      OBJECT = 'VBBK'.
      ID = '0001'.
      EN = 'EN'.
      CALL FUNCTION 'READ_TEXT'
        EXPORTING
          CLIENT                  = SY-MANDT
          ID                      = ID
          LANGUAGE                = EN
          NAME                    = TDNAME
          OBJECT                  = OBJECT
        TABLES
          LINES                   = LINES
        EXCEPTIONS
          ID                      = 1
          LANGUAGE                = 2
          NAME                    = 3
          NOT_FOUND               = 4
          OBJECT                  = 5
          REFERENCE_CHECK         = 6
          WRONG_ACCESS_TO_ARCHIVE = 7
          OTHERS                  = 8.
      DELETE LINES WHERE TDLINE IS INITIAL.
LOOP AT LINES.
IT_ORDER-MSG1 = LINES-TDLINE.
EXIT.
ENDLOOP.

Sales tab in Sales order header

Hello Gurus
When i create a sales order and delivery number for my warehouse. the the 'Delivery status' field of Sales tab in the sales order header data is automatically getting updated 'Fully delivered' .If i create a sales order with out saving the entry and if i go to 'Delivery status' field to check for the delivery status it says 'Not delivered'
Can you please let me know how this field is getting updated .Is there a config where i can control this .
Thanks

Hi,
Once you create a delivery for the respective line item for same qty the delivery status will be change to fully delivered.
But when you create a sales order in VA01 and before saving you see the status its " Not delivered" because the line item deliver has not been donr ( delivery document not created). Its an standard SAP behavior.
Also check the copy control in VTFA in update document flow field at item category level
Hope this will help you to resolve your query!!
Regards,
Krishna O
Edited by: Krishna O on May 28, 2010 7:16 AM

To add Billing Plan at Sales Order Header Level

Dear All,
Our requirement is such that for a project, we need to define a billing plan at header level of sales order.
As of now we are defining billing plan at sales order line item which are having accunt assignment to WBS elements.
Pl. let me know whether we can add billing plan at SO header level and if it is possible then how to do it. Because right now there is no tab available for "Billing Plan" at SO header level.
If we can add it then will it be valid for all item levels?
Need your help.
Regards
Ratna Palit

SPRO - SD - Billing - Billing Plan - the first 5 config nodes (Define Billing Plan types / Define Date descriptions / Assign Date categories / Maintain Date Proposals / Assign Billing Plan types to Sales Doc types) are applicable to you.
this is pretty tranparent for a reference.
What else is required?

Bdc for sales order header text

we need to write a bdc program for va01. In that we need to
upload header text also .
So please kindly tell me how to upload flat file to va01 along with
header text.And how we need to declare the flat file.
if it is not possible through bdc then tell me how to do with bapi.
thank you so much for all the replies

Hi,
Using BDC, You can not uplaod sales order header text. You can upload the header text using FM
CREATE_TEXT.
Here giving sample code. This code is written for Material master text. You change this code according to your requirement
REPORT ZMM_INSERT_LONGTEXT.
*Internal table to hold long text...
DATA:
BEGIN OF T_UPLOAD OCCURS 0,
    MATNR LIKE MARA-MATNR,             " Material number
    ID(2) TYPE C,                      " Identification
    LTEXT LIKE TLINE-TDLINE,           " Long text
END OF T_UPLOAD,*Internal table to hold long text....
T_LINE LIKE TLINE OCCURS 0 WITH HEADER LINE.DATA:
   W_GRUN LIKE THEAD-TDID ,            " To hold id
   W_OBJECT LIKE THEAD-TDOBJECT VALUE 'MATERIAL',
                                       " To hold object id
   LV_VALUE(70).                       " Value to hold material number
START-OF-SELECTION.* This perform is used to upload the file
PERFORM UPLOAD_FILE.* This perform is used to place the text in MM02 transaction
PERFORM PLACE_LONGTEXT.
*&      Form create_text
* This routine used to create text in MM02 transaction
* Passed the parameter w_grun to P_C_GRUN
*                 and lv_value to P_LV_VALUE
FORM CREATE_TEXT USING    P_C_GRUN
                           P_LV_VALUE. DATA:
    L_ID LIKE THEAD-TDID,
    L_NAME(70). MOVE : P_C_GRUN TO L_ID,
         P_LV_VALUE TO L_NAME. CALL FUNCTION 'CREATE_TEXT'
       EXPORTING
         FID               = L_ID
         FLANGUAGE         = SY-LANGU
         FNAME             = L_NAME
         FOBJECT           = W_OBJECT
*      SAVE_DIRECT       = 'X'
*      FFORMAT           = '*'
       TABLES
         FLINES            = T_LINE
      EXCEPTIONS
        NO_INIT           = 1
        NO_SAVE           = 2
        OTHERS            = 3
IF SY-SUBRC <> 0.
    CLEAR LV_VALUE.
ELSE.
    DELETE T_LINE INDEX 1.
ENDIF.ENDFORM.                    " create_text*&---------------------------------------------------------------------*
*&      Form upload_file
* This routine is used to upload file
* No interface parameters are passed
FORM UPLOAD_FILE . CALL FUNCTION 'UPLOAD'
   EXPORTING
*     CODEPAGE                      = ' '
*     FILENAME                      = ' '
      FILETYPE                      = 'DAT'
*     ITEM                          = ' '
*     FILEMASK_MASK                 = ' '
*     FILEMASK_TEXT                 = ' '
*     FILETYPE_NO_CHANGE            = ' '
*     FILEMASK_ALL                  = ' '
*     FILETYPE_NO_SHOW              = ' '
*     LINE_EXIT                     = ' '
*     USER_FORM                     = ' '
*     USER_PROG                     = ' '
*     SILENT                        = 'S'
*   IMPORTING
*     FILESIZE                      =
*     CANCEL                        =
*     ACT_FILENAME                  =
*     ACT_FILETYPE                  =
    TABLES
      DATA_TAB                      = T_UPLOAD
     EXCEPTIONS
       CONVERSION_ERROR              = 1
       INVALID_TABLE_WIDTH           = 2
       INVALID_TYPE                  = 3
       NO_BATCH                      = 4
       UNKNOWN_ERROR                 = 5
       GUI_REFUSE_FILETRANSFER       = 6
       OTHERS                        = 7
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF. SORT T_UPLOAD BY MATNR ID.
ENDFORM.                    " upload_file
*&      Form place_longtext
* This routine places the text in MM02 transaction
* No interface parameters are passed
FORM PLACE_LONGTEXT . LOOP AT T_UPLOAD.    T_LINE-TDFORMAT = 'ST'.
    T_LINE-TDLINE = T_UPLOAD-LTEXT.
    APPEND T_LINE.    IF T_UPLOAD-ID EQ 'BT'.
      MOVE T_UPLOAD-MATNR TO LV_VALUE.
      MOVE 'GRUN' TO W_GRUN.                   "Test ID for Basic data text
      PERFORM CREATE_TEXT USING W_GRUN LV_VALUE.
    ENDIF.    IF T_UPLOAD-ID EQ 'IT'.
      CLEAR W_GRUN.
      MOVE T_UPLOAD-MATNR TO LV_VALUE.
      MOVE 'PRUE' TO W_GRUN.                      "Test ID for Inspection text
      PERFORM CREATE_TEXT USING W_GRUN LV_VALUE.
    ENDIF.    IF T_UPLOAD-ID EQ 'IC'.
      CLEAR W_GRUN.
      MOVE : T_UPLOAD-MATNR TO LV_VALUE,
             'IVER' TO W_GRUN.
                                                  "Test ID for Internal comment
      PERFORM CREATE_TEXT USING W_GRUN LV_VALUE.
    ENDIF.
ENDLOOP.ENDFORM.                    " place_longtext

How to determine a change to a Sales Order Header Text?

Hi All,
Is it possible to compare text entered on a Sales Order Header with what was stored previously?
I know I can use READ_TEXT to retrieve previously stored text but how do I compare with what was entered at VA02?
I'm at VA02, I'm selectin 1 line item. then I'll go to menu Goto->Header->Additional Data B -> Text tab.
when i click save..how do I compare the text entered with what was stored previously?
Any ideas? thanks alot....its kinda urgent.
Message was edited by:
        Slow ABAPer

Hi
Try this in a exit:
TABLES: STXH.
DATA: T_LINES     LIKE STANDARD TABLE OF TLINE,
      T_OLD_LINES LIKE STANDARD TABLE OF TLINE.
* Read current text
STXH-TDOBJECT = <OBJECT>
STXH-TDNAME   = VBAK-VBELN.
STXH-TDID     = <ID>.
STXH-TDSPRAS = <LANGUAGE>.
CALL FUNCTION 'READ_TEXT'
EXPORTING
*   CLIENT                        = SY-MANDT
    ID                            = STXH-TDID
    LANGUAGE                      = STXH-TDSPRAS
    NAME                          = STXH-TDNAME
    OBJECT                        = STXH-TDOBJECT
*   ARCHIVE_HANDLE                = 0
*   LOCAL_CAT                     = ' '
* IMPORTING
*   HEADER                        =
TABLES
    LINES                         = T_LINES
EXCEPTIONS
   ID                            = 1
   LANGUAGE                      = 2
   NAME                          = 3
   NOT_FOUND                     = 4
   OBJECT                        = 5
   REFERENCE_CHECK               = 6
   WRONG_ACCESS_TO_ARCHIVE       = 7
   OTHERS                        = 8.
IF SY-SUBRC = 0.
* Read the old text (before saving)
DATA: BEGIN OF STXL_ID,
           TDOBJECT LIKE STXL-TDOBJECT,
           TDNAME   LIKE STXL-TDNAME,
           TDID     LIKE STXL-TDID,
           TDSPRAS LIKE STXL-TDSPRAS,
         END OF STXL_ID.
STXL_ID-TDOBJECT = STXH-TDOBJECT.
STXL_ID-TDNAME   = STXH-TDNAME.
STXL_ID-TDID     = STXH-TDID.
STXL_ID-TDSPRAS = STXH-TDSPRAS.
IMPORT TLINE TO T_OLD_LINES
    FROM DATABASE STXL(TX)
         CLIENT   SY-MANDT
         ID       STXL_ID.
IF T_OLD_LINES[] <> T_LINES[].
* A change was made
ENDIF.
ENDIF.
Max

System should Not copy sales order header text

Hi all,
My requirement is system should not copy sales order header text while copying sales order to sales order with same order type.
for example i have order type OR - standard type with 500 line items with reference to that same sales order we are creating another order with same line 500 line items,but requirement is system should not copy source document header text in to target document header text,
Do you have any standard functionality to avoid this or we need to go exit
Regards
Nishad

Hi,
You can do it via standard SAP configuration.
Transaction VOTXN.
In the access sequence you have the corresponding Text ID added with "Text Object" VBBK. That's the reason why you are copying text.
Change the entry.
Check below link on how exactly to do that. This doc says about how to copy customer text to the sales order. But procedure is same for you as well. Just the object is different.
[Text type config|http://learnsaptips.blogspot.com/2010/09/text-type-configuration-in-sap.html]
Hope it helps!
Best regards,
Rahal

Sales Order header still booked when lines are already closed

Similar Messages

Maybe you are looking for