Alphanumeric Document number for Sales order

Dear Experts,
I got a requirement, The sales order number after saving the document the SO document number should be SO ( Alphabetic) 00012074 (Numeric) ie. SO00012074,
The numeric portion will come from the number range assigned for that document and Alphabatic portion should come depending on the transaction code and document type.
in SAPMV45AFZZ User-exit
FORM USEREXIT_NUMBER_RANGE USING US_RANGE_INTERN.
This exit triggers before call function 'NUMBER_GET_NEXT' that generates document number for the current document and return to the field vbak-vbeln and finally this is the document number, In the debug mode if I change the number for example 0000012074 to SO00012074 runtime I can get the expected number and also it is saved in the system. But in the real time it is not possible as this coding in not any user-exit.
So I can't use this user-exit for the to get alphanumeric number in the document.
FORM USEREXIT_SAVE_DOCUMENT
This exit triggers after the generation of document number. In this user exit if we change the document number for example 0000012074 to SO00012074, it shows the expected number after saving the sales order but it is not actually saving in the database. Means if we try to open the same SO for example SO00012074 in va02/va03 it is showing
SD document SO00012074 is not in the database or has been archived but if we try open 0000012074 in va02/va03, we can get the document.
We can use this user-exit but if we change the value of vbak-vbeln in this user-exit finally it is not saving in the system.
Can anybody help me how I can achieve the requirement ?

bro...
You have got an option to copy the program the standard program into zprogram....
goto se38 and copy the program into a z program....and in doing so copy everything from the ctandard program ie vaients,documentation and function module etc.
now change this z program to meet your need....
both way if you dont make lot of changes you will get same performance with your work done
regards

Similar Messages

Default document currency as per document type for sales order

Dear All,
We are facing problem in Default document currency as per document type for sales order,
Our requirement is not to give currency in customer master & set it as default document currency as per document type,
for example: Document type 'OR' default currency 'INR',
                     Document type 'ZEU' default currency 'EUR',
                     Document type 'ZUS' default currency 'USD',
                     Document type 'ZNP' default currency 'NRP,'
                     Document type 'ZAF' default currency 'RAND,'
Is it any how possible in standard setting ?,
Regards,
Sai

Hi,
The system proposes the sales document currency from the customer master record of the sold-to party. You can change the currency manually in the document or change in currency in customer master. If you change the currency, the system recalculates prices for the entire document.
to determine different currrency in sales docuement you need to write an user exit and then overwrite the docuement currency copied from customer master. Try user exit 'USEREXIT_MOVE_FIELD_TO_VBAK' under include MV45AFZZ for this change.
with regards
vivek.

How to enter serial number for sale order line which is in shipped status

Hi All,
We have 2 different items which are defined as Serialized at Sale order issue at item definition.
In one sale order,User has forgot to add serial number to one of the item at Ship confirm stage.
He has entered serial number correctly to other item.
Now the both Sale order lines are in Shipped status if we view them through Shipping>transactions.
I am technical guy and new to OM.Could you please let me know the process to enter the serial number for the item to which user has missed it
Thanks,
Satya

Hi Satya,
Since the item is already shipped, you cannot enter serial number for this line.
you have to enter serial numbers after pick confirm only.
check this note
How to Enter Serial Numbers in the Shipping Transactions Form [ID 1235403.1]
As a workaround for the previous lines do RMA and try to receive the goods back to your subinventory.
For all new transactions follow the above notes.
Thanks
-Arif.

Serial Number for SALE ORDER

Hi..
In this scenario , I have to create sale order for 20 qty which it should trigger production order for the same quantity as it have many sub assemblies. sub-assemblies here mean sub batch orders. and for the same qty , serial numbers got generated. So once the stock posted in the storage location , Now the delivery has to be created in VL01N. at this time , user may change the ship to party in delivery order.But this cannot be changed (as per standard) in Delivery ship-to. If sometimes User reduces the quantity the serial number generated will get deleted. But next time when the user created the order , serial number deleted cannot be generated again , but the client do not want to miss any serial number , even the ones got deleted. how to handle this?
Thanks,
KP.

hi
this is to inform you that
you can achieve this by creating a Z table in delivery level when ever user deletes or decreases the delivery quantity then the Z table has to get activated and should store the deleted serial numbers and relevant details which are shown below
logic here is:
when ever your creating a sales order quantity with delivery quantity if it is lesser than sales order quantity then the difference serial numbers will et stored in that Z table. which are used for some other purpose.
these are the z table fields considered:
S.No. sales order number sales order quantity delivery number delivery quantity differene quantity including serial numbers.
please tal to your abaper and update the forum
hope this clears your issue
balajia
Edited by: balaji timmampalli achari on Nov 29, 2010 1:14 AM

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

Table for Sales Order BOM

Hello Friends,
I would like to know the database table which stores Sales Order BOM details.
Actually I want to print the BOM Header Text in my output smartform. For this, I am using the below data.
Language : EN
Text Id : KZU
Text Object : BOM
Text name : Combination of SY-MANDT 'K' and BOM in transaction CS62.
I dont know from where should i pick up this BOM Number.
Thanks,
Salil

Hi
check the tables STPO and STKO
you may find the BOM number for sales order
also use the Table KDST to link the Sales order to BOM
and also use the table MAST to find the link to MATERIAL BOM by taking the sales order material
Regards
Anji
Message was edited by:
 Anji Reddy Vangala
Message was edited by:
 Anji Reddy Vangala

How to look for sales order number if I know outbound delivery number?

How to look for sales order number if I know outbound delivery number?

Hi ,
If you want to see the Sales order Number from Outbound delivery or invoice,go to their respective T-codes,say for example,
for delivery,Goto Tcode: VL02N / VL03N.There you will find Document Flow Icon,click on that,or press F7.
You will get a window,there you can see the Sales order Number before your outbound delivery Number
With Thanks and Regards,
Priya

How to get the document number for a ware house order.

Hello gurus,
how to get the document number for a ware house order. [if GI is posted refering that WH order] .. is there any report?
Thanks in advance

There are several options. When you post a Goods Movement, you can use LB12 -display Transfer Requirement for material document or LB11 Display TR for material.
Depending on how your system is set up you may have gotten a Transfer Order automcatically. In this case you can look at LT24 - Transfer Order for material.

Configration documents for Sales Orders

Hi Experts,
Please help me to understand for the concept for Sales orders.
IF any one is having nay customizing documents it will be helpful
Thanks once again,
Regards
Prajith P

Hi prajith,
Try this link, http://help.sap.com/bp_crmv12007/CRM_DE/BBLibrary/html/BBlibrary.htm
you can get some document to read.
Regards
senthil

Query for Sales Order Analysis

Dear Experts
I have written a Query for Sales Order Analysis and would like to have help on this.
The query is used for generating daily report for Sales Order on number of documents (Sales Order), total amount of sales orders and total GP of Sales Order. The query is written as below:
SELECT T0.[DocNum], SUM(T0.DocTotal) AS 'Total', SUM(T0.U_Total_GP) AS 'Total GP'
FROM ORDR T0 WHERE T0.[DocDate] =[%0] GROUP BY T0.[DocNum] ORDER BY T0.[DocNum]
where U_Total_GP is a UDF for storing the GP of each order.
After executing the query, a selection criteria of date appears and after a date is selected, the report shown information required. However, the query does not calculate column total for total amount and total GP. Although I know the total for each column can be displayed by pressing "Ctrl" + Click on the column title, it would have to be done from time to time.
Therefore, I would like to modify my query in order to calculate the column totals when executed. Are there any suggestions for this?
Thank you
Regards
Elton

Hi Elton,
Try this:
SELECT T0.[DocNum], SUM(T0.DocTotal) AS 'Total', SUM(T0.U_Total_GP) AS 'Total GP'
FROM ORDR T0 WHERE T0.[DocDate] =[%0] GROUP BY T0.[DocNum]
Union ALL
SELECT '', SUM(T0.DocTotal) AS 'Total', SUM(T0.U_Total_GP) AS 'Total GP'
FROM ORDR T0 WHERE T0.[DocDate] =[%0]
ORDER BY T0.[DocNum]
Thanks,
Gordon

In which table,i could find order quantity for sales order..??

In which table, i could find order quantity for sales order..??
and also in which table i could find delivery for sales order..
need help..??
Moderator message: please search.
Edited by: Thomas Zloch on Feb 23, 2012

Check the table AUFM.
Give the order number in AUFNR.
For movement type 261 (GI) & 101 (GR), you can get the material document number (MBLNR), Material (MATNR), Qty (MENGE) & UoM (MEINS).

Want to add number of sales orders in a COPA report or form

Hi All
I created a COPA report that has two columns: sales from sales orders & sales from billing documents. Now I want to add columns which shows number of sales orders that make up sales. Can any one explain me , how can we acheive this With a user exit, .
thanks in advance for looking into this

Hi Steve,
Walter is very right in saying so.
In SD module itself you can get some reports like this.
Even in COPA you will get these kind reports. But if your company is a big company and have lots of sales orders,
Then you will have serious problems with System performance issue.
When you define that sale order is a segment level character, then system will ear up the resources and take very long time in executing the reports.
But for some reason this requirement is a must case, then it is very simple
you define Sale order in either form or report,
then give the variable parameters like Co.Code, Period etc. you will get all the sales orders details for the selected period
But think about not going for it before you make up your mind
Best Regards
Surya

How to restrict the Number of sales orders in theTCode:VL10A whil creation

I'm creating the Delivery by using the batch job with program: RVV50R10C Here I need to restrict the number of sales orders numbers while creating deliveries for sales orders
Like system should pick the sales orders (sales documents) from 1 to 100 OR 100 to 200
Please advise me how to do it and what changes I need to do it

Hi,
Aslo, you can see Note 198137 - VL10: Customer-specific enhancements / user exits. As is for SO, check subroutine LV50R_VIEWG03. If cf_subrc = 1 thin this SO isn't seen in list.
***INCLUDE LV50R_VIEWG03 .
*&      Form POSTAB_VEPVG_FILL_USER
FORM POSTAB_VEPVG_FILL_USER
     USING    IX_LIST_PROFIL    TYPE      SHP_VL10_LIST_PROFIL
              IX_PARAMETERS     TYPE      SHP_VL10_PARAMETERS
              IX_SELECT_OPTIONS TYPE      SHP_VL10_SELECT_OPTIONS
              IT_ENQUEUE        TYPE      SHP_VL10_PACKAGE_T
              IX_SD_ORDER       TYPE      SHP_VL10_SD_ORDER
              IS_VEPVG          TYPE      VEPVG
     CHANGING CS_POSTAB         TYPE      SHP_VL10_ITEM
              CF_SUBRC          TYPE      SYSUBRC.
CF_SUBRC = 0.
* cs_postab-zzfield = ......              "add new field to List
* if xxxxxxx = yyyyyyy.
*    cf_subrc = 1.                         "Exclude this index from List
* endif.
ENDFORM.                    " POSTAB_VEPVG_FILL_USER
I hope this helps you
Regards
Eduardo

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 configure rescheduling for sale order quantities

kindly explain how to configure rescheduling for sale order quantities that are created last month. kindly explain. i am in urgent.
regards,
g.v.shivakkumar

Hi,
Short text
Rescheduling sales and stock transfer documents: by material
Description
The 'Rescheduling' program (SDV03V02) processes sales document items that are contained in the item directory for the material. It takes into consideration open items and schedule lines from stock transfer items, stock transfer scheduling agreements and purchase order requests (items only), referred to hereafter as stock transfer documents, for the materials.
All sales documents for the material that are still open are selected. This means that the material index must be activated for at least all sales document types, whose items may have requirements. All stock transfer documents or items for the material that are still open are also selected. Open in this case means for example, that there is no deletion indicator, that the item from a stock transfer purchase order request cannot be labeled as completed or that the quantity delivered and posted to goods issue for the item in a stock transfer purchase order is the same as the amount ordered. An availability check can only be carried out if a checking rule is assigned to the document type - if this is not the case, the document or document item is not checked.
Checking rule 'A' is used as a basis for rescheduling sales orders (exceptions to this are rush orders they use checking rule B, and orders with individual customer stock; they use checking rule AE). Stock transfer documents use the checking rule that is assigned in Customizing for Purchasing. It is important that the scope of checks is consistent for both the stock transfer documents and the sales documents and that they do not exclude each other, as this can lead to incorrect test results. An example of an incorrect setting would be: The scope of check for checking rule 'A' checks delivery schedules for stock transfer purchase orders and stock transfer purchase requests, however the scope of check for the checking rule for the stock transport scheduling agreement does not.
The items and schedule lines found in the selection are sorted according to 'Priorities' - document category, delivery priority, creation date of the item or schedule line (for stock transfer purchase orders and delivery plans) entered on the selection screen or according to the schedule line date of the earliest schedule line with order quantity, document number and item number and then transferred to the availability check. Priority 1 is highest priority and priority 5 the lowest. Stock transfer purchase order requests are sorted after stock transfer purchase orders and scheduling agreements, as they are less binding. This means that when you have identical sort criteria such as delivery dates, the stock transfer purchase order item is checked first and then the item from the stock transfer purchase order request.
The preset option 'Unconfirmed documents required' only carries out rescheduling for materials for which there is at least one unconfirmed transaction.
You can use the parameters 'Sorting criteria delivery date' to define whether sorting is carried out with the order quantity after the creation date of the item or the delivery date of the earliest schedule line.
If you mark the 'Simulation' field, the checked documents are not saved. Instead a results list is generated and saved. However, the availability check for the corresponding documents continues as if saving has taken place already, that is, that the simulated list corresponds to the actual one.
Under 'Options' on the selection screen, specify whether sales documents and/or stock transfer documents should be processed. For stock transfer documents you can enter whether stock transfer purchase orders and scheduling agreements should be processed at item or schedule line level:
Processing at item level:
All open schedule lines for the item are read and collected, then transferred to the availability check. To sort and prioritize documents, you do not need each individual schedule line. It is sufficient to have the item or data from the first schedule line. All open schedule lines for the item are processed and checked.
Example of processing at item level:
Sorting: Date (Delivery date first schedule line) - Document number - Document item
Doc. cat. Doc. number Doc. item Doc. schedule line Delivery date PO        4500000012      10               0001              26.01. PO        4500000012      10               0002              26.02. PO        4500000025      20               0001              28.01. PO        4500000025      20               0002              02.02.
You can see that the second schedule line for document 4500000025/20 from 02.02 was processed after the second schedule line for document 4500000012/10 from 26.02. This is because all open schedule lines for an item are read and processed. The first schedule line from 4500000012/10 has the earliest delivery date, therefore it has priority.
Processing at schedule line level:
Each open schedule line for an item is entered in document sorting in accordance with the values entered under 'Priorities'. The availability check is carried out for each individual schedule line.
Example for processing at schedule line level:
Sorting: Date (delivery date first schedule line) - document number -document item
Doc. cat.    Doc. number Doc. item Doc. sched. line Del. date PO           4500000012    10             0001           26.01. PO           4500000025    20             0001           28.01. PO           4500000025    20             0002           02.02. PO           4500000012    10             0002           26.02.
Here you can see that each schedule line was sorted according to its delivery date. Note that this type of processing requires more runtime due to the individual checks and more frequent saving.
The results of rescheduling are saved, as long as the program was not started in simulation mode. When calling up from the 'Sales' area menu or when directly starting via the development environment, the iniator is informed via a dialog box that he has just started a process that changes data. He can then decide whether or not he wants to continue.
Checking procedure for stock transfer documents:
An availability check of stock transfer documents in rescheduling is carried out in accordance with the check carried out when manually creating a document. If, however, the required quantity for a schedule line is not available on a particular date and will not be ready until later, new schedule lines are created for the stock transfer purchase orders and scheduling agreements, containing the relevant data. New items are created in this case for stock transfer purchase order requirements. The total sum of schedule line quantities for a processed schedule line corresponds to the schedule line quantity of the original schedule line.
First example: Using a stock transfer purchase order item with a schedule line:
a) Status of item before rescheduling run:
Del. date PO quantity   Confirmed quant Confirmed del. date 23.07.      50 items       0 items              -
==> This now affects the stock/requirement situation:
    - Goods issue is posted for the material in the delivering plant on the 23.07.
    - A purchase order of 10 items was created for the material in the delivering plant. Delivery is expected on the 29.07.
b) Status of stock transfer purchase order item after rescheduling run:
Del. date PO quantity   Confirmed quant   Confirmed del. date 23.07.     40 items      40 items            23.07. 29.07.     10 items      10 items            29.07.
==> The first schedule line was changed in accordance with the results of the rescheduling availability check. Only 40 of the 50 original items could be delivered on the 23.07. Therefore, a new schedule line is created for the rest on the 29.07. for 10 confirmed items.
Second example: Same output situation as the above example.
==> There is now a change in the requirement/stock situation:
A purchase order for 10 items is created for the material in the delivering plant. Delivery is expected on the 29.07. A further purchase shows another 40 planned items on the 30.07.
   Status of stock transfer purchase order item after rescheduling run:
Del. date PO quantity Confirmed quant Confirmed del. date 29.07.     10 items       10 items          29.07. 30.07.     40 items       40 items          30.07.
==> The first schedule line was changed in accordance with the result of the availability check for rescheduling. The original delivery date is set to the date confirmed in the ATP check. A new schedule line is created for the remaining 40 items, that are available on the 30.07.
Note:
Any set fixed delivery date and quantity indicators and creation indicators for schedule lines or items are 'inherited' by newly created schedule lines. Assuming that the original schedule line was fixed in the above example (since it is created manually), this indicator is also set for the newly created schedule line.
If shipping scheduling is activated for a stock transfer document type, this is also implemented for newly created schedule lines, with the exception of route schedule determination. This means that in the current version of the program no route schedule has been determined for a schedule line containing a route schedule for which new schedule lines may need to be created.
The results of the run are issued in the form of a list, which is also saved, so that the results can be controlled at a later date. This is done using the function 'Evaluate rescheduling', but it is only a good idea to do this after the first rescheduling has taken place. You can restrict selection requirements but these can however affect the runtime. You can use this function to analyze the saved list until the next rescheduling run, which writes over the result. If you start rescheduling in the background, a spool file with the result list referred to will be created in the corresponding setting. You can see this in spool management.
Output
A list of changed documents, a list of documents in which an error occurred during processing and as a result were not changed, can be called up via the menu 'Edit - Error log'. If in a subsequent evaluation a restricted selection is carried out, a note appears at the end of the list to say that not all document items are displayed.
You can set the scope of the list under the menu option 'List' in the list display. You can view improvements, deteriorations and the whole list. Before the documents can be included in one or either of the restricted lists, the date or quantity has to have changed so that the item can be contained in both the list of improved or deteriorated documents.
You can use the interface for changing transactions and the order list to navigate. Use 'Back' to exit the list and 'New selection' to return to the selection screen.
Recommendation
You should only start this program occasionally and use very restricted selectin criteria during working hours as it requires enormous system resources.
Note
The columns for 'New date' and 'New confirmed qty' only contain entries if the dates or quantities have changed.
As the system only runs the change check (dates/quantities) per line in the original list, an item whose backlog has increased in the list of improvements. This occurs, for example, if the whole quantity can be delivered at once but at a later date. In this situation, the system determines an increase for the line when it compares quantities.
Regards,
Amrish Purohit

Alphanumeric Document number for Sales order

Similar Messages

Maybe you are looking for