Incompletion log for sales order

Hi, Experts.
I am looking for the user-exit for incompletion log for sales order, If the user choose DC = '20', so the incompletion log will check the field of Incoterms.

hi,
yes shiva sir is right.
Form USEREXIT_CHECK_VBKD
      This Userexit can be used to add additional logic for         *
      checking the sales details for completeness and consistency. *
      US_DIALOG - Indicator, that can be used to suppress         *
                    dialogs in certain routines, e.g. in a          *
                    copy routine.                                   *
      This form is called from form VBKD_PRUEFEN.
just adding to the context:
there are two ways of doing it.
1. hard code - vbak-vtweg - DC = '20' then system has to check the fields vbkd-inco1 = knvv-inco1, vbkd-inco2 = knvv-inco2.
2. create a Z table and link the user exit to check what the entries are there in Z table and react according to the entries. before that in Z table should be with this fields called - vtweg, inco1 &2.
hope this clears your issue.
balajia

Similar Messages

No Incompletion Log for Sales Order with net value as zero

Hi all,
There is an Inbound IDOC which creates a Sales Order.
When we check the IDOC, we find that it has got 4 line items (E1EDP01). However, for all the items except the third one (for example), the segment E1EDP05 is filled. In the segment E1EDP05 the field KRATE contains the corresponding net value for the respective line items.
Then when we check Sales Order which is created, we find that the third line item (for example) has the net value as zero. In this case, ideally there should have been an entry in the Incompletion Log. However, it does not happen so.
I suppose the issue is with the third line item in the IDOC for which the segment E1EDP05 is not present. I have debugged the corresponding FM is IDOC_INPUT_ORDERS, but was unable to find any clue.
Please let me know the reason for this.
Thanks and regards,
Anishur

In routine interpret_idoc_orders the item conditions are filled by calling
WHEN 'E1EDP05'.
       MOVE IDOC_DATA-SDATA TO E1EDP05.
       PERFORM ZUORDNEN_ORDERS_E1EDP05.
In case KRATE is empty no values are transferred to the order
    IF NOT E1EDP05-KRATE IS INITIAL.
      PERFORM IDOC_CUR_MOVE USING E1EDP05-KRATE XKOMV-CURRDEC
                                  XKOMV-KOEIN
                                  XKOMV-KBETR D_FLAG_P-PKON.
    ENDIF.
If that is a valid scenario, you need to adjust your incompletion procedure in customizing to include the net value on item level so any missing value is reported.
If this is not supposed to happen you might want to hook into one of the user exits in the idoc and in case KRATE is missing let the idoc fail.
Hope that helps,
Michael

User exit to update the incompletion log in sales order for pricing error

Hi experts,
I have to check the some mandotory pricing conditions in sales order, if that conditions are not exist in sales order then i need to show the information message as well as i need to update it in incompletion log of sales order. (incopletion log we can see on menu bar 'EDIT' or ctrl+F8 on main screen of VA01). So that user can save the sales order but it will be in incomplete status.
I have completed it upto showing the information message using user exit 'MV45AFZZ', but after this i don't know how to update it in incompletion log of sales order for pricing. I tried to update in tables VBUK-UVPRS, but i am not getting the desired result.
Please anyone can tell me how to update it. In which user exit i can update the incompletion log.
Thanks and Regards,
Vicky.

Hi Vinod,
I am sending you my code please check it,
   if TKOMK-SPART = 10.
    if XKOMV is not INITIAL.
      clear v_JEXP.
    READ TABLE XKOMV with key kschl = 'JEXP'.
    if sy-subrc = 0.
      check XKOMV-kwert = 0.
      message i003(ZT) with 'Value should not be 0 for conditioin type JEXP'.
      v_JEXP = 'X'.
    else.
      message i003(ZT) with 'Maintain the mandatory Conditioin type JEXP'.
      v_JEXP = 'X'.
    endif.
    if v_JEXP = 'X'.
XVBUV-MANDT = sy-mandt.
XVBUV-POSNR = '000010'.
XVBUV-TBNAM = 'VBAP'.
XVBUV-FDNAM = 'PRSOK'.
XVBUV-FEHGR = 20.
XVBUV-STATG = '06'.
XVBUV-FCODE = 'PKON'.
XVBUV-SORTF = 9999.
XVBUV-LFDNR = 0000.
XVBUV-UPDKZ = 'I'.
append XVBUV.
    endif.
endif.
endif.
Please suggest something to solve this.
Thanks and Regards,
Vicky.

Incompletion log for new order type

Can you tell me for setting the incompletion log for an order type what is the procedure

Hi Pooja,
Let me make it very simple for you.
Firstly, you will have to go into customizing SPRO - SD - BASIC FUNCTIONS - LOG OF INCOMPLETION ITEMS.
1) Select Define Incompletion Procedure.
You will be asked whether to create at Sales Order Header or Sales Order item
Choose Sales Order Header, and either copy an existing incompletion procedure or click on new entries and assign a number range and then define the table and field names which you want to be compulsoraily inputted in the Sales Order at the time of saving.
I am sure you know how to get the table and field names, press F1 in the relevant field and go to techincal details, and get it from there.
Now if say you want to issue a warning to the user if he doesnt input any of the fields that you have entered in your incompletion procedure, just make sure you tick in the warning field.
Also based on your business scenario, you can decide what level of action you want to take if the Sales Order is not entered with all the relevant field names that you just maintained in your incompletion Log.
This can be handled by the column called " Status Group "
Based on the status group you can decide whether to restrict Billing of the order or Delivery as so on against each table and field name that you must have maintained in your incompletion procedure.
Just make sure the tick that you see in Status Group, means that particular activity is restricted.
Now once you finalize all the table and field names along with status group and warning messages, now is the time to assign this incompletion procedure against your sales order document type in transaction VOV8 (Please note we are using VOV8 since we earlier defined this procedure for Sales Order Header)
If you would have choosen Sales Document Item, then you would had assigned this incompletion procedure against your item category in transaction VOV7.
Now once this maintenance is done, you are ready for testing.
I hope this will help you.
If it does please dont forget to reward points for contribution.
Regards
Ravi

Work flow for incompletion log in sales order/ quotations

Hi all,
I am looking for a standard workflow for checking in-completion log in sales order and quotations. I found one object type BUS2032/2031 which is more related to removing certain master data or Customizing settings related errors in "internet" sales order and quotation. My requirement is to check the flag/ status in the incompletion log which is turned on as a result of "locking" the characteristics in VC in sales order/ quotation
Any pointers will be helpful.
Thanks
RG

Hello,
If you know the BOR (e.g. BUS2032) then you can check for workflows that have an event of that BOR as triggering event by looking in table HRS1212 where OTYPE = WS and OBJTYP = BUS2032.
You can then look at the workflow (e.g. via PFTC_DIS) to see if it does something similar to what you're looking for.
Standard workflows usually aren't enough, you may have to copy and adjust, or create a new one.
regards
Rick Bakker
hanabi technology

Incompletion log for rejected order lines.

I've one order with 3 lines items, and the 3rd line missing Plant Value (WERKS). Whe I rejected the 3rd line, the order still shows on V.02, and the incompletion log on the order still show the order is incomplete. So it stops me from further processing the whole order.
Is this SAP standard functionality? Do I miss any configuration to allow incompletion skip the rejected lines?
Thanks.

Charles Zheng,
This is default you will have to enter plant to proceed further, Based on the plant your shipping point will get configured in the sales order based on which your delivery will happen.
It is manadatory that you need to maintain PLANT in sale order. wihtout which yes you can save the document. But delivery is impossible.
It is standard Feature. You will have to maintain Plant either in Customer Master record, CMIR or Material Master from where the plant will come automatically. If Suppose you have not mainatined in masters the you will have to enter it manually..
It is Standard Format...
Regads
Sathya

Function Module for Incompletion Log in Sales Order

Hello All,
Can anybody provide me the function module when the sales order is incomplete due to Incompletion log.
Thanks,

HI,
Use the functional module: RV_MISSING_DOCUMENT_DATA.
Goto SE37 and press F7, input the material/order number etc in the import data field VBCOM.
And then execute the module. By using this module we will get all the incomplete items in an order.
If you want list of incomplete orders, use V.02 transaction code.
Regards,
Satya.

Incompeltion log for sales order over view screen

dear all,
i have a problem in incompletion log , my requirement is i need the incompletion log to be trigered in the sales order over view screen .
The senario is :
There is a excel sheet maintained in the    sale order over view screen - extras tab - Documents - there excell sheet will be maintained and   from that the item will be selected .
is there any way to inclued this   field and table in the log of in completion terms in incompletion procedure . or is there any
user exist to be involved for this
kindly guide me how to go about it so that the error or warning msg   is triggered when this incompletion is checked
regards
kumi

Hi Kumi,
Do you mean you want to check whether DRAW-DOKNR or DRAD-DOKNR is filled with value?
If yes, I don't think standard incompletion log could fulfill your requirement since only check for VBAK, VBKD, VBAP and VBEP could be defined.
I also checked Userexit_save_prepare (MV45AFZZ). Table DRAW is not available. DRAD is empty.
Sorry but I could not provide more positive answer.
Best regards,
Smile
Edited by: Smile Zhang on May 25, 2010 3:39 PM

Creating change log for sales order

hi all,
i want to create change log for any given sales order if it exists.
can any one tell me how to do that??

Hi Gouri,
CDHDR and CDPOS are the tables for all change history.
CDHDR contains the details such as who made the change, when, using what tcode and the change type ie. update, delete.
CDPOS contains the field name which was changed, its old value and its new value.
The change document object is VERKBELEG for sales documents.
The object value is the SD document number with leading zeros.
The following link will be also useful.
http://www.sap-img.com/ab024.htm
Regards,
Nitin.

Updating processing log for sales order header output

I want to prevent a custom sales order confirmation from printing when the order has not been approved. When the user requests the form to print in the background, I want to update the processing log to have a red light and a message indicating the order has not been approved, so it cannot be printed. When I pass an error message to the protocol processing, the update is terminated and my changes to the sales order are lost. Is there a way to update the processing log, show the red light, and not get the hard error?
Thank you in advance.
Jay

Setting the return code after the protocol update did the trick.

Change to existing sales order - There is no incompletion data for sales document

we have just started TM in our sandbox system. When we change an existing order we get the following message:
There is no incompletion data for sales document and the order change does not get sent to tm. Creating a new order and changing all works fine. Is there something to be done with existing orders?

Hello John,
Have you tried to use the report TMTRQINITIALSENDING?
Rgs, Marcelo Lauria

Getting the incompletion problem in sales order.

Dear Gurus,
We have created the sales order with the 16 item and by mistake we have punched the wrong values for 14, 15, and 16 item. After that we had deleted the item no. 14, 15, and 16 from the VBAP , VBEP and VBUP tables.
Now when we go to particularly that order and change something and trying to save that order we are getting the incompletion log for 14 , 15 and 16 item (schedule lines , loading date and material availability date).
when we try to complete the incompletion log we are getting the message the item does no exist.
please help
Regards
Pawan

Hi,
Delete the order and create the new one.
Thanks,
Pramod

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.

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

Incompletion log for sales order

Similar Messages

Maybe you are looking for