Scheduling problem in LSMW for Sales Order
I am doing LSMW for Sales Order using the BAPI method.
I am able to upload the item details along with their quantities also but the problem that I am now facing is the scheduling problem.I am unable to schedule the item quantities, only the last quantity passed is taken as the final quantity and the consolidated quantity is also getting ignored.
I am using E1BPSCHDL structure, in this structure I am mapping Itm_number , req_date and req_qty(scheduled qty).....
in the structure E1BPSCHDLX, the same fields are mapped as 'X'.
in the structure E1BPSDITM, I am mapping the item info along with the consolidated qty(TARGET_QTY), but this is getting ignored and the last scheduled qty is taken as the final consolidated qty and the rest scheduled qty data is getting rejected.
Please do help... I dont know why this problem is coming... tried n number of alternatives but of no hope... do try to help me
with regards,
Daya.
Check the format of your date and check the format expected.
sometimes you can have diff like YYYYMMDD, MM.DD.YYYY,...
Look at the converted data.
Hope this helps,
Erwan
Similar Messages
-
Dear all,
I have a question, can LSMW batch change some data in sales order line item?
For example, there has a sales order with 20 items. I have to change the material group in item 10 and 50, can i achieve this by LSMW?Dear all,
I still cannot found item in my recording. In my recording just show below information:
I am not sure if " BDC_OKCODE =ITEM" means item?
SAPMV45A 0102
BDC_CURSOR VBAK-VBELN
BDC_OKCODE /00
VBAK-VBELN 17380
SAPMV45A 4001
BDC_OKCODE =ITEM
BDC_SUBSCR SAPMV45A
VBKD-BSTKD 1
BDC_SUBSCR SAPMV45A
KUWEV-KUNNR 211011
BDC_SUBSCR SAPMV45A
BDC_SUBSCR SAPMV45A
RV45A-KETDAT 2008.06.23
RV45A-KPRGBZ D
VBKD-PRSDT 2008.06.23
VBKD-ZTERM 0001
VBAK-AUGRU 002
BDC_SUBSCR SAPMV45A
BDC_SUBSCR SAPLV45W
BDC_SUBSCR SAPMV45A
BDC_CURSOR RV45A-KWMENG(01)
BDC_SUBSCR SAPMV45A
SAPMV45A 4003
BDC_OKCODE =T\02
BDC_SUBSCR SAPMV45A
BDC_SUBSCR SAPMV45A
BDC_CURSOR RV45A-KWMENG
RV45A-KWMENG 2
VBKD-PRSDT 2008.06.23
SAPMV45A 4003
BDC_OKCODE /00
BDC_SUBSCR SAPMV45A
BDC_SUBSCR SAPMV45A
BDC_CURSOR VBAP-MATKL
VBAP-PRODH 50...510..5100
VBAP-MATKL 730
VBAP-SPART 10
VBAP-KONDM 11
VBKD-KDGRP 12
VBKD-KONDA 11
VBKD-PLTYP 11 -
Dear Friends,
I am trying to upload sales order data using transaction VA01 by Batch Input Recording method in LSMW. But I am not able to get line items due to the fact that I am not able to assign two source structures. So i am trying to upload by Abap Coding in LSMW. But still I am not able to get the Item Data. So Kindly help me in this.
With Regards,
H.Krishnanuse the first method (Direct Input)
Object : 0090 (Sales)
Method : 0000
Programname: RVINVB10
In structure relations u can find header and line itemas.
before that define 2 structures.
===================================================
After creattion of one structure..
again click on create button> now it will ask samelevel/lowerlevel..give ur option>then u can add the fields in the next step.
pls.reward if it helps u and close this thread
Thanks
Eswar
Message was edited by: Eswar Kanakanti -
LSMW for sales order uploading
Hi Guys,
I need to upload single time sales order detials into SAP through flat file, is any sap standard LSMW methods are available or I need to develop a Z program.
Could you please give your suggestions?
Thanks,
Gourisankar.Hi gourishankar,
LSMW is not a bad one, but striaght BDC programme with BAPI would be the
best
so see this link it may help you.
http://www.****************/Tutorials/LSMW/Bank/page1.htm
thanks
karthik -
Problem in lsmw for purchase order (direct input)
hi friends,
i am trying to upload po using lsmw by direct input method.
only problem is it is not taking delivery date properly.
at the end error message is 'plz enter valid delivery date'.
can any one tell me why it is happning.
thanks
sonuCheck the format of your date and check the format expected.
sometimes you can have diff like YYYYMMDD, MM.DD.YYYY,...
Look at the converted data.
Hope this helps,
Erwan -
LSMW --direct input for sales order
Hi frenz,
We are facing a problem in mapping the fields, sold-to-party and ship-to-party in structure BVBPAKOM.
I have already tried using partnerfunction(PARVW) and custno(KUNNR). Even then i got an error 'Specify ship-to-party or sold-to-party'. Can anyone help me regarding this problem.
Helpful answers will be rewarded with points and wishes.
---praveen.hi,
join this link dude
LSMW DIRECT INPUT FOR SALES ORDER
cheers,
sanjay. -
MRP-Delivery Schedule for Sales order is not updating in Production order
Dear Experts,
I have created Sales order and maintained delivery scheduling, Then Run MRP through MD50,
We received Planned order then through this we have converted to Prodcution order.
When we observe the delivery schedule for sales order under assignment Tab in Produciton order which is showing zero instead showing line item of Delivery schedule.
I am able to see Sales order and Line item but i am not abel to get any delivery schedule line item.
Please suggest where settings are missing.
Thanks in advance
Regards
DonDear Experts,
Please provide me solution.
after Running MD50 transaction against Sales order.
If I maintained different Scheduling Line Item for First Line item of Sales order.
The Respective Scheduling Lines should update against Each Production order which has converted from Planned order.
Thanks in advance.
Regards
DON -
Hi,
Does anybody know how to switch off ATP ONLY for Sales Orders?
Customer would like to have ATP for deliveries, but not for sales orders. This means whatever delivery date will be entered during SO creation, system will accept it without ATP. On the other hand if there is nothing on stock system should create delivery with "delivered qty" = 0
The only transaction which connects ATP type (02 in this case) with checking rule (here: A- Sales order) is OVZ9. But I cannot switch off ATP there. I can only define different settings for sales order and delivery.
If I change settings in OVZ0, then it will switch off ATP for both: sales order and delivery
Customer has only one requirement class ZXX, so in OVZ) I can switch off ATP, but unfrotunatelly for both (sales order and delivery).
In standard I see requirement type 031 (Order requirements) and 011 (Delivery requirement), so I think this is the way I should go.
I've checked SPRO here:
Availability Check and Transfer of Requirement --> Transfer of Requirements --> Determination of Requiremenr Types Using Transaction.
The problem is that for one item category I can assign only one requirement type (ZXX in this case).
How do I switch off ATP only for sales orders?
Is it possible?
regards
RafalDear Rafal,
If your requirement is "whatever delivery date will be entered during SO creation, system will accept it"
then try this,
Go to IMG-SD-Basic Function-Delivery Scheduling & Transportation Scheduling-Define Scheduling by Sales Doc Type.
Select the Sales Doc type & make the "Delivery Sch" field blank.
By this the system will accept the date whatever you put. (for that sales Doc type only)
Pls let me know, whether the problem is solved or not.
Thanks -
Hi All,
I've worked with LSMW to record transactions in the past, but I'm unsure of what the best approach is for sales orders. Our requirement is to upload a simple tab-delimited text file that contains the PO#, PO type, Material, Grid (we are using AFS), Name/Phone/Address of the ship-to party, and shipping notes text.
My main question is concerned with handling the multiple line items on the orders. I have seen some posts here that suggest using one LSMW to do the header data (VA01), and then a second to do line item data (VA02). However, I need this to be one step. I see there is a BAPI with Business Object BUS2032, but I have not worked with that method.
Any idea on the easiest way to complete this? I'd like to have a simple step for a user to run to automate entering 15-20 orders a day. Any help is appreciated, thanks!
JHi,
Firstly you can create the sales orders using the BPAI with header data and for line item details you can go for anothere BAPI
BAPI_SALESORDER_CHANGE. hope it will work.
~linganna -
Planned material price in case of production order for sales order (MTO)
Hi,
In case of production orders created for sales order, the planned price for a component (BOM) material gets picked as per following:-
1. If there is no entry in EBEW for the component (that is, there is no previous GR for the component) for that sales order, then plan price is picked up on the basis of planned costing variant.
2. In case there is an entry for the component in EBEW (there has been a previous GR for the component with reference to the sale order) then the plan price for the component is taken from the EBEW table (first GR price) and system ignores the costing variant.
The above is as per my observation. Please validate if this is correct or not.
The requirement is that even if there has been a previous GR for the component (there is an existing entry in EBEW) the system should take the plan price on the basis of costing variant and not from the EBEW table.
How can this be achieved? Is there a user exit that can force the system to read the costing variant before looking into the EBEW table?
BR
AbhiHi Ajay,
Yes i had considered it but I'm not sure If it will help.
Because the main problem here is that system is ignoring the costing variant itself and instead picking the price from EBEW table. So changing the costing variant (validation variant) may not help.
Moreover i don't want to valuate with my own strategy. I want the plan price to be equal to standard price of material from material master. Basically MBEW instead of EBEW.
Any clues?
BR
Abhi -
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,
MindaugasPlease 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 -
Problem in Printing of Sales order amount with program ZRD_RVADOR02
Hi,
We have one output type for printing the order aknowledgement for customer which is printing all details from sales orders for this we have made a program and form by copying the std. one Program : ZRD_RVADOR02 and form form : ZS1_RVORDER01_RD it is std. if we remove z we have done some little modification for header detail like company code and added ondition type etc.
for sales order basic price condition is PR20 and addiotnal price condition is PRXX in sales order the final price is addition of both but when both the price are same it is printing only single condition value and if both are different then it is priting addition of both means if PR20 and PRXX both are 5000 it is priting 5000 onlu actually it should print 10000 AND IF BOTH ARE DIFFRENT LIKE PR20 : 5000 and PRXX : 5000.01 then it is printing 10000.01 properly .
what can be the problem.
regards,
zafarHi,
Can u help on this issue.
regards,
zafar -
Using MD50 to run MRP for Sale Order
Dear all,
I have some problem when using MD50 with Mill Product Industry.
When SAP system not activate Mill Product yet. I used transaction code MD50 to run MRP for Sale Order, the system have generated planned order for multilevel. But when SAP system have activated Mill Product, I used transaction code MD50 to run MRP for Sale Order, the system only generate planned order for single level. I think that we have to configure something based on Mill Product Industry. So can you help me for this
Thanks, RegardsHi,
Check with following links which may help you resolve your issue :
http://www.sap.com/sme/whysap/industries/millproducts/index.epx
http://help.sap.com/saphelp_di471/helpdata/en/4e/1796374b088e5ce10000009b38f8cf/frameset.htm
http://help.sap.com/content/documentation/industry/docu_is_mill.htm
Regards,
Tejas -
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.shivakkumarHi,
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 -
DIServer insert operations for sales orders with error
DIServer insert operations for sales orders with
That even though the insert is inserted DocDueDate DocDueDate it says error.
Subtracting the value of the format 'yyyy-mm-dd', 'yyyy/mm/dd', 'mm-dd-yyyy', 'mm/dd/yyyy' put all reporting
When the input is entered DocDueDate ShipDate also put together ... but I get an error.
The error message 'env: Receiver-10Enter due date [ORDR.DocDueDate] 171AddObject2EEE7D98-AB71-464A-93AB-933F0AD3D4DC'
Purchase order entered into the normal value because the xml is missing or wrong with you.
Please answer all the possibilities that can be resolved
This Xml used.
"<BOM>" +
"<BO>" +
"<AdmInfo>" +
"<Object>oOrders</Object>" +
"</AdmInfo>" +
"<QueryParams>" +
"<DocEntry />" +
"</QueryParams>" +
"<Documents>" +
"<row>" +
"<DocType>I</DocType>" +
"<DocDate>2012-01-11</DocDate>" +
"<DocDueDate>2012-01-11</DocDueDate>" +
"<CardCode>CD00001</CardCode>" +
"<Address>Anymode</Address>" +
"<DocCurrency>KRW</DocCurrency>" +
"<Comments>[sales orders] LGU TEST</Comments>" +
"<TaxDate>2012-01-11</TaxDate>" +
"<JournalMemo>JournalMemo</JournalMemo>" +
"<Address2>Addr</Address2>" +
"<BPL_IDAssignedToInvoice>1</BPL_IDAssignedToInvoice>" +
"</row>" +
"</Documents>" +
"<Document_Lines>" +
"<row>" +
"<ItemCode>ACDT0100ET</ItemCode>" +
"<Quantity>1</Quantity>" +
"<Price>5000</Price>" +
"<DiscountPercent>10</DiscountPercent>" +
"<WarehouseCode>A100</WarehouseCode>" +
"<VatGroup>A2</VatGroup>" +
"</row>" +
"</Document_Lines>" +
"</BO>" +
"</BOM>";I had the same error change the Date to the format yyyymmdd, and problem solved.
Maybe you are looking for
-
When i open itunes it gives me the option to download the new version 10.3. my computer will not support 10.3. i can't by pass the download to continue with my current version of itunes. i've trashed and reinstalled 8.2.1 twice. any solutions?
-
When I Conditional Supress the page footer. It occupy space in report
I am designing Crystal report with multiple page footers.Initially I have suppressed all page footer. Each page footer is un suppressed against a specific Test Id (db Field). I have done this with formula for each page footer. The problem is when Pag
-
Please help! Thanks!!!
-
How to unistall x code at mac pro
evening , how to remove x code at mac pro 13". thaks
-
Have CAM/CAS in OOB L2 Virtual Gateway working with AD SSO assigning the access VLAN based on group membership in the AD. Need to get the login scripts to run. The information for adding a delay as per page 9-6 of the CAS manual v4.1.3 doesn't work.