Archiving Process for Sales Order

Hi,
We have this new client. Archiving was previously working & has suddenly stopped. Logs are also unavailable as they have been erased.
We just have a list of Batch Jobs which contain the following Programs.
1. RSARDISP - The Scheduling Job
2. S3VBAKWRS - Archiving Program (Input or output error in archive file /oracle/STP/ixos/exchange/RSD04210.220142.BATCHBA)
3. RSARCH_STORE_FILE
We need to run these batch jobs, in order to find out where the error is occurring.
We can see the old already archived documents, by ckicking on Enviorment -> Display Originals on VA02 screen
Questions:
1 What is the sequence in which we need to run these programs?
2.Is this the entire list of steps in order to enable archiving for Sales Orders
3.I am not sure if SARA is being used to schedule, or is it just these Batch Jobs with the programs. How can I know the exact process that was employed previously
Any assistance is Appreciated
Thanks

Hi
If you don't have any documentation, I suppose that you are using the object SD_VBAK, and your client is using SARA. Check these points:
- The settings for the auth.objects are in tcode AOBJ. See the reports for preprocessing, archiving and deletion. You must mantain selection variants to call them with SARA.
- See mantain networks graphic. You must archive and delete all documents in the flow before to archive SO.
- See the settings in tcode VORA (customizing tcodes) where you do the settings for residence time (Number of days which must elapse in order to archive the sales document).
I hope this helps you
Regards
Eduardo

Similar Messages

How to see archive data for Sales order

Hi all,
I am working on PS , network is created with sales order 10911. the components are added while sales order created, but after that someone deletes the sales order, because now it is showing oder does not found, where i get the entreis for sales order.
Regards,
Khushi.

Hi Khushi,
To see the archived data for sales order , go to transaction code SARA.
Choose object name as SD_VBAK.Click READ.
It will show a screen giving a name of program and option to execute in background or foreground.
It will help you to get information about archived sales order data.
Hope it helps you.
Thanks,
Sarita singh Rathour
Edited by: Sarita Rathour on Aug 28, 2009 7:46 AM

Down Payment processing for Sales orders using Milestone Billing Plan

Hi,
The business scenario is as follows.
The delivery for the sales orders are to be created only after the pre payment( a percentage of the total sales order value) is made by the customer.
Hence the sales orders while creation are blocked for delivery creation using credit block by means of a userexit.
The credit manager checks the blocked sales orders using VKM1 transaction and verify if there are any payments made by the customer to cover this pre payment to be made.
If it is enough to cover then he releases the sales order manually for delivery creation.This is a complex process since there are too many sales orders and the payments made by the customer may not match the amount to be paid(it can be greater or lesser).The customer just pays a huge amount which is to be distributed among the sales orders for pre payments.
Later, when the invoice is created, the customer account is cleared manually using F-32 transaction for the oldest open invoices.
Here again there is a huge manual effort involved since he need to distribute the amount against the invoices using oldest open item principle.
As a solution we are planning to implement "Down Payment processing for Sales orders using Milestone Billing Plan".
Is this the right solution?
Can you please give the steps in detail to implement this functionality for above scenario?
We are using SAP 4.7 version without Project Systems.
Thanks in advance.
Regards,
Ragesh

Hi Ragesh
Check the links where you will get the entire down-payment configuration
[https://forums.sdn.sap.com/post!replydownpayments ]
Regards
Srinath

Auto Replishmnet process for Sales Orders

Hi,
Can any body suggest, how we can follow "Auto Replishmnet process for Sales Orders" for Particular customers with for required articles.
Please suggest replishment process for sales orders.
Regards
Kiran kovi

Hi,
This process is available in SAP Retail. Help says you can use it for manufacturing as well.
You can read up more about VMI: Customer replenishment here:
http://help.sap.com/saphelp_erp60_sp/helpdata/en/86/37e622f09b11d18ca1080009d10d9a/content.htm
Hope that helps!
Regards,
Naveen

ATP Re-Run in background processing for sales order

Hello All,
In sales order i need to re run the ATP check for the quantity confirmation in background processing.
Scenario is :
I have created orders with order quantity 100.
while creating the order stock for the same material was only 20 so ultimately it will not confirmed the quantity.
After the some period i m increasing stock of same material by 120. Now, same order which i created before can be confirmed as i need only 100 quantity in that. but for the same I need to manually run the ATP again and then it will confirm the quantity.
instead of manually re run the ATP again i want to do this activity in background processing so that it will automatically confirmed the stock once inventory increased.
Is there any provision in sap to avoid this manual task with the help of background processing or any program?
Thanks and Regards,
Rasik

Hi,
This can be achieved by rescheduling the orders .
<< Moderator message - Cut and paste response from http://help.sap.com/saphelp_470/helpdata/en/93/744c0c546011d1a7020000e829fd11/content.htm removed and points unassigned. Plagiarism is not allowed in SCN >>
You reach the Sales screen.
Select Environment ® Backorders ® Rescheduling ® Execute.
You can also simulate the backorders for rescheduling before confirming by selecting the simulateevaluate option.
Prerequisite for rescheduling the line items of the order is that at schedule line you should not flag the field fixed date and quantity field. Also for ATP you must have defined the scope of check with checking rule BO(i guess) for that particular plant in combination of checking group .
Hope this will help you.
Thanks and Regards,
Atulkumar Dagade
Edited by: Rob Burbank on Jan 24, 2012 10:16 AM

Outbound idoc process for sales order using message control

Hi All,
    I am changing sales order using VA02 , while saving sales number IDOC is creating but I am unable to see the data filling into segments. I think idoc is triggaring in background.
Can you please tell how I can see the data filling in to segments
Thanks in advance,
SN

keep the break point in the program RSNAST00
at this particular code.
perform (tnapr-ronam) in program (tnapr-pgnam) using returncode
                                                         us_screen
                                                         if found.
and also Activate update Debugging , before pressing the save button in VA02.

How to implement Approval hierarchy for Sales Order in Order Management.

Hi,
We need approval process for sale orders in Order Management module. Currently we are using credit HOLD option for orders at shipping level. The issue we are facing now is we can not cancel those orders who contains Service Line item in it while on HOLD. The restriction raised at the time of cancelling the order that the Line Item is "fulfilled". Service line item's get fulfilled.
Is that any other possibility to have Approval hierarchy for Sales Orders in Order Management Module? If it is possible can anybody share the related document or implementation guide?
Thanks with anticipation in advance.
Many Regards
Kaleem Bhatti

I copied the standard order header workflow and the "Book Order, Manual" workflow to custom workflows. I then modified the "Book Order, Manual" workflow to put another completely custom workflow (call this "Approvals") in between the "Book Eligible" and "Book" steps.
The "Approvals" step assessed the sales order, changed the order header to the pending approval flow_status_code, and sent out the appropriate notifications. The "Approvals" step returned a Complete/Incomplete where complete would proceed to "Book" and incomplete would go back to "Book Eligible." The new workflow was then assigned to the order type needed. I don't still have access to that environment (job change) or I would give more definite instructions.

Confirmation/Back order processing in Sales Order

Hello All,
Need some inputs on the Schedule line confirmation and the back order processing for Sales Order
Scenario 1
Sales order created but there is no stock in Storage location. Based on our settings Sales Order confirmed for a future date(say 10 days) based on the delivery/lead time.
Also sales order goes on credit block. Next we receive stock in storage location.
Now when we release the credit hold it is not doing the confirmation autmatically. I know it can be done but dont know the settings or config where as soon as the Sales order is released from Credit hold then it should do the availibility check and confirm the Order (for todays or toms date.)
Scenario 2:
Sales order created but there is no stock in Storage location. Based on our settings Sales Order confirmed for a future date(say 10 days) based on the delivery/lead time.
Next we receive stock. We would like to confirm the sales order automatically by a program instead of going in individually in each sales order.
What Tcode/program can do this availibility check and confirm the sales order for todays date. Is this a back order processing or rescheduling. Need information on this process..
Thanks
SAP Fans...

HI Rahul
When you create the sales order and if stock is not confirmed then ,system will give the next delivery date and you can do the backorder processing for that sales order . So backorder processing is done only for Open orders
Regards
Srinath

Release for Sales order

hi all
i have a doubt regarding the sales order. when PO is created there will be a release strategy for that. Like same is there any release strategy for sales orders. if it is there is it a mandatory process for every sales order or exactly can anyone let me know in which cases the release process for sales order is used.
regards
rag

Dear Tarun,
You can set the rlease strategy for the sales order through maintaining the Status profile settings.
It is not mandatory process ,you can have this based on the business requirement.
This releasing process can be used when the client wants the specific user need to check the sales order before creation of the delivery and then release that to the delivery.
For more details about Status Profile process you can go through this SAP help
http://help.sap.com/saphelp_47x200/helpdata/en/dd/560629545a11d1a7020000e829fd11/frameset.htm
I hope this will help you,
Regards,
Murali.

Steps for sales order to MRP Run

Dear all,
Could you please explain what are the steps to process after creating sale order to run MRP and delivery?
Regards
Rajasekaran

Hi Rajaseshekhar,
Following will be detailed end-to-end process steps.
                 Create Sales Order Entering Finished Goods Material
                 Master
Auto Generate Alert(E-mail) to Production Planner
                Create ‘Order BOM’ by Copying Finished Goods BOM (Sales
                 Order Item). Amend by deleting/adding Items in Order BOM at all levels
Auto Generate Alert(E-mail) to Product Cost Controller
Recalculate 'Sales Order Costing' to reflect changes to ‘Order BOM’
Auto Generate Alert(E-mail) to Production
Run Sales Order MRP
Convert Planned Order to Production Order
Capacity Leveling
Release Production Order
Pick Components (Picking List)
Confirm Assembly Activities
Post Goods Receipt (Production Order)
Delivery Processing for Sales Order
Create Invoice
Hope ite helps,
Jatin

Post order processing for sales document is not yet complete

hi,
sap gurus,
i am facing the error while saving the sales order and this ticket is unique and it is saying that
"post order processing for sales document is not yet complete".
please help me in this regard.
and it is blocking the order for further processing.
regards,
balajit

I dont think this is a standard error message. Some exit is applied for sale order to meet some requirements. You need to check with your ABAPer.
In fact, you can conclude yourself based on the error message number. If it starts with Z, then the above holds good.
thanks
G. Lakshmipathi

Processing of Sales order output type BA00 processes another Z output type for acknowledgement.

Hi Friends,
I am facing below mentioned issue and request your suggestion to solve it
Via processing of sales order output type BA00 another Z output type is processed and acknowledgment is sent to SAP inbox( sost).
This is working incase of manual addition of BA00 output type and via standard program " sd70av1a", but this functionality is not working when i am calling this standard program in a Z report via batch job.
with the below code-
DATA: name TYPE tbtcjob-jobname.
         DATA: number TYPE tbtcjob-jobcount.
         DATA: print_parameters TYPE pri_params.
         name = 'ORDER_PRINTING'.
         CLEAR: range1.
*REFRESH: range.
         range1-sign = 'I'.
         range1-option = 'EQ'.
         range1-low = 'BA00'.
*        range1-high = 'ZBA1'.
         APPEND range1 TO range.
         CALL FUNCTION 'JOB_OPEN'
           EXPORTING
             jobname          = name
           IMPORTING
             jobcount         = number
           EXCEPTIONS
             cant_create_job = 1
             invalid_job_data = 2
             jobname_missing = 3
             OTHERS           = 4.
         IF sy-subrc = 0.
           SUBMIT sd70av1a WITH rg_kschl IN range
                           WITH rg_vbeln IN order_tab
                           TO SAP-SPOOL
                           SPOOL PARAMETERS print_parameters
                           WITHOUT SPOOL DYNPRO
                           VIA JOB name NUMBER number
                           AND RETURN.
           IF sy-subrc = 0.
             CALL FUNCTION 'JOB_CLOSE'
               EXPORTING
                 jobcount             = number
                 jobname              = name
                 strtimmed            = 'X'
               EXCEPTIONS
                 cant_start_immediate = 1
                 invalid_startdate    = 2
                 jobname_missing      = 3
                 job_close_failed     = 4
                 job_nosteps          = 5
                 job_notex            = 6
                 lock_failed          = 7
                 OTHERS               = 8.
             IF sy-subrc <> 0.
             ENDIF.
           ENDIF.
         ENDIF.
       ENDIF.
In this case only BA00 is getting processed but Z output type created for sending acknowledgment is not triggered.
Please suggest how can i achieve the required functionality.
Thanks,
Surya

Solved myself..
Thanks.
Br,
Surya

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

Tcode for Sales Order Output(collective processing)

Hi
What is the tcode or program to print sales orders collectively, similar to VL71 for deliveries & VF31 for invoices.
Regards
Uma

Hi Uma
There is no such T code for sales order print.
You can use SE38-> run RSNAST00 program for sales order output (collective processing).
try and revert.

Workflow for Sales Order Release via Status Profile

Dear all,
i want to make a workflow for sales order which have 4 User Status in One status profile.
Once Event triggered for sales order
1.   Mail should go to main authority with sales order number.
2. Once authority will do some changes in the required field then he/she changes
     the user status-1 from defauts as per line Item and mail should go to department no-1 (Head authority).
3. Once again same changes in sales order but now user status-2 from user status-1
     as per line Item and mail should go to department no-2 (Head authority).
4. Once again same changes in sales order but now user status-3 from user status-2
     as per line Item and mail should go to department no-3 (Head authority).
5. Once again same changes in sales order but now user status-4 from user status-3
     as per line Item and mail should go to department no-4 (Head authority) .
and parrally for each changes of Status mail should also go to User (Event Creator).
6. Finally mail sholud go to User as you are permitted to do next business transaction for this sales order
Please tel me the process as i am very new this topic and i am always going to stuck in Binding.
please help me out.
Thank You

Hi Neeraj,
First of all start with SWELS and SWEL T-Code to check if any standard event is getting triggered or not. If event is getting triggered, then use the same event to trigger the workflow; otherwise create a custom event of BO and use the same to trigger the workflow.
Hope you are aware of T-Code SWO1 and delegation of BO. The BO used for your requirement will be BUS2000115.
As you want the workflow to get triggered only for one status profile and one of its status, so use check function module. There set the condition for you status profile and status.
The FM which you will be using the most is CRM_ORDER_READ. To read the status, you can also use CRM_STATUS_READ_OW.
Now simply make the approval steps in the workflow using activity. In the activity, you can use the standard method USERSTATUSPOPUP to send the workitem for approval. In each step use the same activity with different agents as approvers.
Just go with these things and let me know if you get stuck up somewhere.
Regards,
Guddan

Archiving Process for Sales Order

Similar Messages

Maybe you are looking for