How to release user status for sales documents automatically

Hi All,
We have configured status profile for third party sales document type. This will stop creating PR from sales order. After chaning the status from STP to GO, system will create PR. But the problem here is user is going and changing the object status manully.
The business wants to release at a time many records automatically. Do we have any transaction code which we can use for changing the user status automatically for many orders?
We have tried V.26, but this is just report we can not change the status automatically,
Thanks in advance!
Regards
Lakshmikanth

Hi,
No standard program exists for it, as statuses are always customized.
create a BDC program for status change and run in backgram as batch job.

Similar Messages

How to extract User status for Sales and purchase contracts

Hello,
We need to load the User status linked to sales and purchase contract.
I think that there is no datasource in BI content.
What is the better solution ?
- Enhance a standard datasource like 2LIS_11_VASTH with a status field (This solution is not ok for Purchase contract)
- Create a spécific datasource to extract this status
- Others
Thanks for your help
Best regards
Christophe

Hi,
In your scenario its better to use generic extractor to get the reqd data. This data can than be stored in a DSO on the BI side.
And you can look up for the user status using a routine .
Regards,
Rahul

How to Set User Status of Sales Order at item level.

How to Set User Status of Sales Order at item level by default to 'Purchase Req Not Created' (example)while creating order. Please tell EXIT Name to be triggered & Internal table to be populated.
Thanx,
Srini
Moderator message: please do your own research before asking.
Edited by: Thomas Zloch on Feb 21, 2011 11:19 AM

Mathew,
Here is a document that should help you get started on enhancing 2LIS_11*
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c09d5356-d8c4-2d10-8b84-d24723fc1f0a?QuickLink=index&overridelayout=true
Good luck!

Extracting User Status for Sales Orders

I am trying to extract user status transactional data for sales orders (at both the header and item level). I have been following SAP note 300300 to configure the status extractors and map the BW objects to sales order status data sources (2LIS_11_VASTH & 2LIS_11_VASTI). I think I have set up both R/3 and BW correctly according to note 300300 and the IMG documentation, but I am not getting any values in the info source for the new user status info objects, when I run the extract.
Has anyone successfully done this? If so, do you have any documentation or pointers on how I can get this to work? Or, am I better off creating a generic extractor? Thanks for your consideration.
Sincerely, Hashi Chakravarty

Hello Ravi,
well yes, I can derive the status for that order in the update rules if i show the status as an attribute of the 0pm_order; but basically there will be only the last status shown.
My problem:
a. i report on day 1, the status of the order is REL
b. on day 2 i load the master data for the orders, new status is TECO
c. on day three i want to report in the past and see the status of day 1; that's not possible in this scenario because i'll see the current status (TECO).
So that's why I want to have the statuses in the cube...
The 2lis_17_i3hdr extractor is only sensitive to CRT and TECO statuses, but not to the others (like REL / BLC and so on... :_(( )
I could read the statuses from the JEST and TJ02T tables...but still, if a document status is changed, no delta record is written in the queue...
Thanks,
Tudor

Update vbup/vbuk from user-exit for sales document

Dear All.
Is it possible to update the sales document status for an item (vbup) from a user exit , customer function, badi, or other, in the billing document?
We'd like to make the control of updating the status tables dynamic, rather than based on the confiuration for an exception process.
For example, when service item (order related billing) is partially billed, depending on some conditions we would set the sales order service item to fully invoiced.
In this case vbup-FKSAA = C.
Many thanks!

There is a BAdI LE_SHP_ITEM_STATUS that can change the item status in VBUP. Be sure to read the documentation first. It states
If you use this BAdI to change the delivery item status that was set in delivery
processing, it can affect further processing of the delivery extensively, and
lead to data inconsistencies. Therefore, SAP recommends that you only use
the BAdI to modify your own status fields.
Regards,
Brenda

CRMD_ORDER - How to add user status for searching

Hi Gurus
Our requirement is that we want to search sales transactions in CRMD_ORDER by user defined statuses. Currently I can only search by system status (along with other standard criteria such as created by/direct processing etc). How do I add more search criterias so as to enable searching solely by user status?
Please advise.
Thanks

Hi Jai,
As per your requirement, i suggest u to check the Tx CRM_SRV_REPORT (standard Tcode)
In this report you can change the layout of the screen after executing the report, and choose the user status from the layout.
I hope this will help you
Best Regards,
Madhup

User exits for sales order

Dear all SAP experts,
How to find out the user exits for sales document type? Especially the user exits which are called when we save the sales order.
With best regards,
Allabaqsh G. Patil

Hi,
Also there is user exit to refresh data
USEREXIT_REFRESH_DOCUMENT
       It is always necessary to refresh user-specific data before   *
      the next document will be processed.                          *
      This can be done in this userexit.                            *
      This userexit can be used to refresh user-specific data       *
      when the processing of a sales document is finished           *
      - after the document is saved                                 *
      - when you leave the document processing with F3 or F15       *
      It may be necessary to refresh user-specific data before      *
      the next document will be processed.                          *

How to find out the Accounting document status for sales order

Hi
We have created the sales document by referring the billing document of contract no.Aftre that we have raised invoice for sales document. Now system is generated both invoice , accounting document and the value is appearing against the invoice document. However the status against the accounting document is showing as not cleared. I want to know where we could see this status in Table,
Normally we can see the status in FPLT for contracts since its having the billing plan no. Suppose if the billing plan is not available like S.O , How to check the status in table?
I have refered so many tables but not helping. Since i want to get the uncleared value of accouting document.
Please help me.
Regards
Thenna

Hi Thenna
The accounting document status in the document flow is determined dynamically when you display the document flow,
it's not saved in a specific table.
Here is the relevant logic:
LV05CF01 -> form BUCHHALTUNGSBELEG
IF vbrk-vbeln <> vbfa_tab-vbeln.
   PERFORM vbrk_ermitteln USING vbfa_tab-vbeln.
   REFRESH xbkpf.
   CALL FUNCTION 'FI_DOCUMENT_READ'
    LOOP AT xbseg WHERE bukrs EQ xbkpf-bukrs
                  AND   belnr EQ xbkpf-belnr
                  AND   gjahr EQ xbkpf-gjahr
                  AND   ( koart EQ 'D' OR koart EQ 'K' ).
    ENDLOOP.
            IF NOT sy-subrc IS INITIAL.
SET STATUS TO 'No items are cleared'
              l_xdoc_num-status = 'A'. <<<
            ELSE.
              LOOP AT xbseg WHERE augbl IS initial
                            AND   umskz NE 'A'
                            AND   vorgn NE 'AZUM'
                            AND   ( koart EQ 'D' OR koart EQ 'K' ).
              ENDLOOP.
              IF NOT sy-subrc IS INITIAL.
Set status to 'All items are cleared'
                l_xdoc_num-status = 'C'. <<<
              ENDIF.
            ENDIF.
Regards,
Alex

User status for Service Issue{for particular Sales order} in CRM

Hi Experts,
I've an issue related to the User status in CRM.
I've a Sales Order and I'm creating a service issue for it in CRM.
For the service issue number has some user status and I want to know from where it is coming.
Is there any configuration involved in it, or is it coming from the standard coding part.
Please let me know how to find the user status for a service issue.
Thanks
Subbu

Thank you PePe,
I'm asking about the user status not the system status.
The user status has only the values{open, worked & closed}.
now for a service issue if it is rejected then the user status are automatically changed into "Closed".
So if you have any idea in this please help me.
thanks
Subbu

What is the use of Release Strategy for Sales Document

Hi,
Can i know what is the use of Release Strategy for Sales Document? Difference between lowest level and Highest level.

Hi,
Can i know what is the use of Release Strategy for Sales Document? Difference between lowest level and Highest level.
Lowest Status No: Sale Document can have several statuses at the same time. However, only one of the statuses may have a status number. If another status with a status number is activated; the old status with status number is deactivated. This is only valid under certain conditions. The system makes a note of the status with the highest status number that has been reached up to the present. The "lowest number" of this status number determines which status number a new status must have.
Highest Status No: Sales Document can have several statuses at the same time. However, only one of the statuses may have a status number. If another status with a status number is activated, the old status with a status number is deactivated, provided the new status number does not exceed the 'highest number' defined for the old status number
If you want more clarity try to check below link
http://www.sapfunctional.com/SD/ReleaseStrategy/Index.htm
Regards,
Prasanna

How to delete a document status for a document type

Hi,
May i know how to delete the some document statuses for a document type. Because present we are having many document statuses, In that we want to remove some statuses.please find the screenshot and help me please.
In tha above screenshot, Now i want to keep the highlited one only. Remaining status i want to delete. May i know how to delete and after deleting the statuses, may i get the statuses as per my requirement.
Regards,
Mastan.

Hi,
As per the above requirement, i have deleted some statuses, But now i want in cv02n, the following statuses,
In first step, i have changed the status in cv02n, from work request to Reallocation status. please find the screenshot.
After this step, i want get the status in cv02n, as PPC head Status, But while changing status, i am not getting the status pop box as per my requirement and i got as per below pop screen.
Please guide me how to get the status of PPC head in pop box when clicking the Document status icon. And also please guide on that, if i am deleting the existing statuses, what i need to check.
Regards,
Mastan.

How to Find preceeding Document for sales document

Hi,
Please let me know how to find preceding or subsequent document for sales document.
Thanks,
Mahdukar.

Hi,
For individual document you can go to VA03 ,Vl03n, va02 or vl02n, vf03 or vf02 and click on document flow.
Also you can find the details of preceding document for all the sales documents in the single table VBFA. Tcode -se11 or se16 or se16n.
HOpe this will resolve your query.
Regards,
Krishna O

How to add a default user group for multiple document type's?

Hi,
I am trying to add same default user group for different document types when MA is created. Is there any way to setup using a single "Document Security Template"? Or I need to create different templates for different document types?
Please confirm.
Thanks,
Saloni

Hi Saloni,
Based on what your specific requirement, it might be easier to do it with scripting.
If you are doing it using Document Security Templates, you would have to create a Document Security Template for each of the 6 MA types and assign the default group. Create another one and leave the Document Type field blank, so it will apply to the other 4 MA types that don't have a default group.
Regards,
Vikram

PCUI: Setting system status in sales documents

Hi experts!
For sales documents (e.g. Quotations, Complaints) in PCUI, we lack the possibility to enter the system status. In PCUI, only the user status can be changed. In SAP GUI, both system and user status can be set.
For replication issues, we need to set the system status for quotations to "Released". Any idea how this can be achieved? Is there a way to do so via action profile or so? Any other ideas?
Thanks,
Sebastian

Hi,
thanks for your answer. What you describe is correct for the status complete. If I set the user status complete, the system status is also changed to complete. But if I set the user status released, the system status is "in progress" (and not released).
Do you know where I can set the relationship between user status and system status? Or what do you mean by "the user status that corresponds to the 'Released' system status"? How can I check the correspondance?
thanks,
Sebastian

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
Regards
Eswar

How to release user status for sales documents automatically

Similar Messages

Maybe you are looking for