Good Issue date in the Sales order should 1 day difference from the MBDAT

For the particular customer, i want to have difference of 1 day in between the material availability date & good issue date in the schedule line. As per standard i can't made any changes in route and shipping point. Suppose material availability date in sales order is 22.09.2010 than my good issue date should be 23.09.2010 in the sales order. Any body having any idea how can we handle this case and what are things we need consider impact of this change.
Regards,
Srinivas.

Hi,
I think you can easily enable this in Route scheduling /Delivery scheduling. You have to maintain the load time and pick/pack time as the total of 8hours. If this is done, then after material availability date, one more day will be added and the final day will be considered as GI date.
If you dont want to do this, you only have to enable this by Z by using a user exit where you can add one day to the MBDAT and update that in GI date.

Similar Messages

To populate condition in the sale order or a scenario in the USER Exit

Hi Experts,
I want to write the code in the USER EXIT to add a condition type in the Sale order when the ship-to-party address is changed in the transaction level from the address maintained in the Master data,
So can anyone let me know is there any function module or how will i populate condition type.
I found that the internal table XKOMV contains all the condition types.
Thanks,
Prem

i saw the answer provided by u, i was pleased to find the answered way, so i writing back to u regarding my requirements.
my requirement.
while creating sale order, before entering the screen 4001 where we enter sold to party and material and order quantity, i need to populate these fields from my exit.
i am able to populate the sold to party field from the exist EXIT_SAPMV45A_002 and
INCLUDE ZXVVAU04 .
in the same fashion i need to populate my material filed.
how do i do it

VAT /CST% manually in the sales order,not getting copied to the Invoice

Dear Friends,
If I change the VAT /CST% manually in the sales order,its not getting copied to the Invoice
Thanks
Ivy

Dear Friends,
Thanks for your valuable inputs....
I have maintained the condition record for the combination of delivery plant region and the customer region.......assigned dummy tax code against the Tax condition...therefore I think there wont be any problem in posting billing doc to accounting doc.
There are different combinations,where sometimes the user is liable for 2% CST ....sometimes 4%CST... but I am able to pick one tax value say 12.5% CST across and maintained the tax condition types - manual entry has priority, as allowed the user to change the value manullay as per the user requirement ....
Now if i change the Tax condition value in the sales order ,the same is not reflecting in the Invoice....this also is applying from contract to a sales order...
Please advice me accordingly...
Thanks
Ivy

How to get know the Sales Order IDOC#, if I know the created Sales Order#?

Hi Experts,
Let me know that, How to get know the IODC #, if I know the Sales Order#?
Scenario is that, sales order(say 12345678) was created from Inbound EDI. I also Know the MATERIAL too.
So, How to pull the associated Inbound ORDERS idoc, which is created this Sales order-12345678?
Is it from EDID4 table? or EDIDC? or any thing else?
reples r appreciated.
thanq
Edited by: SAP ABAPer on Sep 8, 2008 5:29 AM

Hello
This can be done much easier using fm SREL_GET_NEXT_NEIGHBORS:
Input:
OBJECT-OBJKEY = <number of sales order> " with leading zeros!!!
OBJECT-OBJTYPE = 'BUS2032'
MAX_HOPS = '01'
Result:
NEIGHBORS-OBJKEY = <IDoc number with leading zeros>
NEIGHBORS-OBJTYPE = 'IDOC'
NEIGHBORS-ROLETYPE = 'INIDOC'.
Regards
Uwe

BAPI to post a Goods issue with relation to Sales Order?

Hi Everyone,
After creating a delivery order, I need a BAPI to automatically post a goods issue for this DO.
I tried using BAPI_GOODSMVT_CREATE but it returns the message 'Goods Movement not possible with mvmt type 601'.
Any advice?
Best Regards,
Junwen

Hi John,
My data are as follows:
GOODSMVT HEADER:
PSTNG_DATE: 30.09.2004
DOC_DATE: 30.09.2004
REF_DOC_NO: had tried 1014000359 or empty
GOODSMVT_CODE: 03
GOODSMVT_ITEM:
MATERIAL: HP0121002
PLAN: 1010
STGE: 10FG
BATCH: BATCH1
MOV: 601
CUSTOMER: 180017
ENTRY_QNT: 1
ENT_UOM: PC
ENT_UOM_ISO: PC
DELIV_NUMB: 1014000359
DELIV_ITEM: 000001
From your feedback, it is possible to use the BAPI to create a goods issue for movement type 601?
Best Regards,
Junwen

Goods issue to customer without sales order or Outbound delivery

Dear all gurus,
I have a case like that: Supposing we don't have neither Sales Order nor Outbound Delivery (because not implement SD, for eg).
Then, we stil want goods issue to customer. So can u advise me how to do: which Tcode, which movement type,...
Thanks,

Hi,
Create a cost center for customer and issue the goods with respect to this cost center in MB1A transaction using movement type 201.
Then all the issues will be tracked based on this cost center.
Regards,
Bharat

Filling the Sales Order Header - Source for filling the dropdown boxes

Hi,
I am trying to design the User Interface for Creation of sales order using the WebDynpro's. I want to know, what are all those BAPI's i need to use to fill the following drop down boxes.
1. Order Type
2. Sales Organization
3. Distribution Channel
4. Division
As i am new to ABAP., and i am from Java background, i dont know much about the BAPIs used to get the above data.
Could anyone let me know the source to fill those dropdown boxes. Thanks in advance.
Thanks,
Raghavendra

Ah,my bad.
Hmmm,i haven't found a BAPI's for filling all your dropdown-boxes with the valid values.
What about using the FM "RFC_READ_TABLE" to read the values for your drowdown-boxes.(only if you don't want to write a Z*-Function).
For examlpe for the dropdownbox "Sales Orgs",you can can start this FM for the table TVKOT.
Is that a possilbe solution for you?
Greetings
Frank Brackmann

In the Production Order, Sales Quotation is displayed not the Sales Order

Hello to All,
I need a kind help from you.
My scenario is as follows
There is a Configurable Material (Finished Product)
Sales quotation (VA21/2/3) were made for this material.
Sales Order (VA01/2/3) with reference from the Sales Quotation were made for this same material.
Now when I run the MRP (MD02) for this material, Planned Orders were created.
Planned orders were converted to the Production Order.
In the Production Order (say in Display mode), under the 'General' tab, there is a segment called 'Sales order'. In this segment, the sales order is being displayed if the Production Order is created for a sales order (MTO scenario).
But, in my case, the Sales Quotation number is being displayed instead of the Sales order.
My Issue which need your answers:
Is it a standard SAP scenario?? I mean, if the production order is created for a sales order and again if the sales order is created earlier with reference to a sales quotation, then in the production order, the Sales quotation is displayed. Is it a standard?? Or it is showing wrongly? I mean, is it like that, always the sales order should be displayed in the Production order and not the sales quotation??
Please suggest so that I can overcome this problem, if at all it is a problem.
Some More Inputs (For your analysis/research):
1. After the MRP run of the material the Planned Order is created. I have checked the planned order, and found tha the assignment of sales document (in this case Quotation) is done in the Planned order itslef. It is visible wthin the "Assigmnet" tab of the Planned Order.
2. For the analysis purpose, I created one stand-alone Sales Order for the same material. I mean, without reference from any Sales Quotation. Then, when I run the MRP (md02), the Planned Order and then production order were created normally, with reference to the Sales order. This just for your kind information.
3. I have checked the pegged requirement of the Production order in the MD04. It is showing the Sales order itself. But, if I see the production order (CO02/O03), it shows sales quotation.
User Requirement:
Evenif, the sales order is created with reference to a Sales Quotation, after MRP run, in the Planned and thereby subsequent production order, the Sales Order should display and not the Sales quotation.
Please suggest.
Thanks and Regards,
Supriyo

Hi
Since your scenario is configurable material, the system takes the reference of sales quotation only. Because the in case of configurable materials the sales quotation is the base and based on the sales quotation the sales order is created and subsequent production order.
This is std SAP and for configurable materials the sales quotation is deciding factor
Krishna

PP: Production Order Qty UOM should be based on the sales order Qty UOM though having Alternate UOMs in material master

Hello PP GURUS I am new to this and i have one issues. I.e., While creating the Production Order, want the unit in the production order should be based on the sales order unit instead of what has been defined in the material master. Since, having 3-4 alternate unit of a material & can create a Sales Order in any one of them.
Also pls let me how to go through
either with the help of ABAP or configuration.
If it is with the configuration pls let me know the solution to arrive.
Eg: Base UOM is KGS
Alt UOMs: SQM, MTR, NOS
Sale order is Prepared with SQM and the same shall be in production order too to produce qty.
Pls help me.
rgds,
Kumar V

Hi
First you have to maintain alternate units in mateial master for that first go in additional data & maintain the alternate units as below..
For example
1200 M2=1 KG For SQM
12 M=1 KG For MTR
3 PC=1 KG For NOS
And then you can get Sales unit field in sales data 1 view enter your sales unit in that field & you will get production unit in work scheduling views as per your desire production units and according to that units your sale order & production order will pick that units & you can proceed accordingly but remember that first maintian the conversion factor as above other wise it will not accept hope that it will help you have a nice day...
Regards,
Reena

Delivery date on the sales order

Hi frnds
I am facing an issue here. When the sales order comes of credit hold the system proposes a new delivery date in the sales order. How can i change the settings to avoid the system from assigning weekends(Saturday & Sunday) as the delivery date????
I have checked that the factory calendar is set for weekdays only and also the propose del date is check marked in VOV8, OVX5 & OX10 have factory calendar asssigned but i am not able to figure out how to restrict the delivery date to weekdays to be proposed by the system.!!!
Am i missing something???
Will appreciate your suggestions.
null

Hi,
The fields needs to be activated in the filed group in accounting.
The path is SPRO -> Financial accouting -> Accounts Receivables and Accounts Payables -> Customer accounts -> Master data -> Preparations for creating Customer master data -> Define account groups with screen layout.
Shiva

FG sales order should consume the PIR of SFGs

Hi ,
I need some advice on following scenario.
My client wants - Make to order for FG material, and Make to stock for SFGs.
So that SFGs are made into stock by putting PIR, and FG production is initiated by sales order and will consume SFG stock.
As per this if sales order is created for FG, then SFGs PIR should be reduced or consumed according.
I had used strategy group for SFG as 40, and for FG as 55 (actually FG is having variant configuration)
So, accordingly now FG production is initiated by sales order, but SFGs PIR is not getting consumed and also a seperate planned order is getting generated for SFG because of FG Dep Req.
Is there any changes I have to make.
Thank you in advance.
regards,
B C Gudageri

B.C.
In Strat 70, the PIRs are not consumed by the sales order, they are consumed by the dependent requirements of the FGs orders (prod order reservations or planned order dep. rqments). In MTO, these requirements are usually analogous to the Sales order requirements.
If this is not happening, you have either altered the standard settings, or you have set up some master data incorrectly.
Go over the strat 70 online help IN DETAIL to make sure you have set up the scenario properly.
http://help.sap.com/erp2005_ehp_04/helpdata/EN/cb/7f940d43b711d189410000e829fbbd/frameset.htm
You can use just about any FG strategy, as long as the dependent requirements are being passed to the SFG materials. 55 won't hurt you, but it doesn't make much sense to enter a forecast at FGS if you are also going to forecast at SFG. Logically, you probably want to avoid forecasting FGs, since this adds excess complication for the planners.
Best Regards,
DB49

Free Goods not appearing in the Sales Order

Hi,
I have created the condition record for Exclusive free goods for a material. However when i create a sales order with the same material, the free goods materials is not appearing.
I did a Free goods Analysis in the sales order and when i checked the field values, I found that for a particular access sequence it says "Access not made ( initialized field)"
Please help.
Thanks.

Hi,
This error usually happens when we donot maintain any of the fields in the access sequence that we use.For Eg., if your access sequence is Sales Org/Dist Channel/Mat group and if you fail to maintain your condition record with the same sequence,you will get this error.Please maintain the condition record with the respective access sequence and you will not get this error.Please try and confirm.
(Also in the above example even if you maintain condition record and didnot maintain material group in the materisl master you will get this error.So check all the possibilities and confirm.)
Regards,
Phani Prasad.

COGS issue in the sales order

Need your help to resolve below issue.
A sales order is created with multiple line items. The user created delivery and invoice document for one of the line item in the sales order. The line item cost was active in the sales order and invoice document. The value was determined from the material master record. The user then created delivery document for other line items in the sales order, but invice document creation ends with an error message that "Sales order is incomplete so billing can not be carried out" VF 069
The first invoiced item has become inactive in the sales order now and the sales order goes into incomplete status. The system is blocking the invoice document creation for rest of line items. Could you tell me why the line item cost became inactive. Also tell me how to resolve this issue.

I dont think,
There is any problem with Cost in Sales order line item.
Cost copied from MMR is statiscial & always in display mode.
Goto VA02- key in order no n press entere.
now from menu bar- Goto- Edit - Incompletion log ( Cntrl + F8).
if any field is missing , then maintain the field to complete the sale sorder.
incompletion log will be maintaiend @ order n item level. check in Item category for the incompletion procedure & check the fields maintained in incompletion procedure in Tx: OVA2.
Regards,
Reazuddin MD

Planned Goods Issue date

Hi,
We have the system set up as follows:
When the user enters the delivery date, and then material, route determination occurs. If, for example, there is a lead time of two days on the route, the Goods Issue date is set to two date before the delivery date.
The user can enter many items.
If, for different reasons, the lead time is only a day, the user has to drill down on each item multiple times to change the Goods issue date. We are looking for a quick way, something similiar to "Fast change of delivery date" to change the goods issue date.
Please share your experineces or proposals on the above problem for the user.
Thanks in advance,
Finbarr

Hi ,
You can use TA - MASS . Enter object type - BUS2032(for sales orders) on initial screen and select sales item data.
Next screen enter selection fields like sales order no and items. After giving order no and item range , execute and enter all new values for any item data fields. After pressing button "carry out mass change", don't forget to press save button.

User Exit in the Sales order create BAPI

Hi,
Can some one help me in telling if there exists a user exit for the BAPI '/AFS/BAPI_SALESORDER_CREATE'.
This is urgent. So, pls. throw some light on this.
Thanks in advance.

Hi
User Exits In Sales Document Processing
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.

Good Issue date in the Sales order should 1 day difference from the MBDAT

Similar Messages

Maybe you are looking for