Transfer posting for sale order

I have Material A Received from customer A 100 mtrs, in Storage location 0001
Customer is telling me to use only 20 mtrs. so i will raise sale order (for the rest of the 80 mtrs he will tell when to issue to prod)
By this time i have to do transfer posting only for 20 mtrs and also i have to create a batch and keep it in 0002 storage location
what is the correct movement type i have to use??

Hi murugan,
I am receiving material by raising PO, then i am doing GR
For eg suppose customer is giving 10000 mtrs, i will raise PO for 10000 mtrs and take the printout of it and i give to him as Receipt that PO number is for eg 1000
i will do GR for 10000 qty against that PO number 1000 and keep it in 0001 str location
in stock i will have 10000 mtrs of customer material
Later after 1 month he will tell me what design has to be printed on the Material
that too he wont give for total 10000 mtrs he will be giving only for 2000 mtrs
for this 2000 mtrs i have to create a batch and i keep it in 0002 str loc
while receiving material the code will be CM01
After receiving the design from the customer we have to do transfer posting for 2000 mtrs and the code will be BC01 batch - 1000b01(shows 1000 is the Tracking number(PO number) B01 Batch 01)
so that we come to know how much material have been received from the customer and for how much metres we have received design
How much is still lying in storage location, tracking will be easy
My question is CM01(customer material at initial stage dont have batch number)
After receiving design for partial quantity to do TP matereial to material for 2000 mtrs fromt received 10000 mtrs.
Material to material TP at that time system should create Batch? sale order also will be created as soon as we receive the Design for 2000 mtrs

Similar Messages

Transfer posting for sales order stock questions. Propose BOM components?

Hello
We are working with a third party subcontracting scenario (SD item category TAB/sched line CB), where a Subcontracting PO (item cat L/acc assign M) gets generated.
At MB1B, I perform a 412E movement to issue components to a sales order.
When I issue components to the sales order, I need to manually enter the component and quanity. I would like the system to propose the component quantity, similar to when I do a movement 541 to a subcontractor.
Is this possible? Any advice would be greatly appreciated !!!
Regards
Ken

Hi
Goto Transaction Code, VOV6--> Choose Sch.Line catagory, CB> Go in to detail--
>There you maintain PR Doc.Type as NB, Acc.***.Catagory as "M" and Itemcatagory as "L",then after completing the sale order, Automatically PR will be created with item cat L and acc assign M ....
Then create PO by refering this PR...
(Before that make sure that you have maintained the link bet. Acc.***.Catagory as "M" and Itemcatagory as "L" in OLME-->Accout Assignment--
> Define combination of Acc.***.Catagory and Item catagory
and also In OLME-->Purchase Requisition---->Define document types -
>you have to maintain the link for converting this PR into PO...)
If you have already maintained BOM, then in PO---> Material data tab---> the BOM will be automatically exploded.
Then you can issue these items to SC Vendor in Transaction code. ME2O
Hope I have cleared your doubts
Reward if useful
Regards
S.Baskaran

GI for sales order stock

Hello Gurus,
I have special stock as sales order stock (stock type E) booked against the particular sales order. Now that sales order is archieved since it is old SO. I want to now issue this special stock, but system gives error message type "SO has been archieved". Is there any way how can I issue this stock?
Thanks

Before you archive anything you should make sure that you have the most recent OSS notes in the system.
Looks like OSS Note 196062 - Sales orders with sales order stock are archived
was not implemented. Hence your system was able to archive such documents because of a program error.
OSS Note 202345 - Transfer posting of sales order stock without sales doc.
may help youo out of this situation.

Miss value FI Posting on Sales Order Transfer Posting movement Type 413 E

Dear Expertise
               I've a problem about sales order transfer posting. My both of Sales order (Source & Destination) are make to order and open with configurable material(KMAT). Both of sales order contain only one item on the same material no.
Assume scenario material vastr
Assume that material vastr is configurable material wait for sales order to fill characteristic and it was maintained standard price value = 1100
                Sales order A has plan cost on material VASTR 1000
                Sales order B has plan cost material VASTR 980
When we make a sales order transfer posting(Transfer from Sales Order A-> B) by transaction MIGO_TR by use movement type 413 E. It can post a transfer complete. But my problem is when I trace to FI-Document
                It was post like this
                Dr. Standard price                         1100
                Cr. price for Sales order A(src.) 1000
                Cr. Cost Variance                          +100
I don't want it to offset with standarad price value. I want it to do like this
                Dr. price for Sales order B(Des.)   980
                Cr. price for Sales order A(src.) 1000
                Dr. Cost Variance                           +20
How can I configure it?   I trial to clear standard price by MR21, System can do it . But I don't want to clear it because it impact to other. I want to know. How can I configure system to take both of plan cost of sales order to offset each other please.
Edited by: Gareth John on Aug 16, 2010 2:23 PM
Edited by: Gareth John on Aug 16, 2010 2:42 PM
Edited by: Gareth John on Aug 16, 2010 2:42 PM

Hi,
411- E- sales order to own stock
412-E- Reversal of 411 E
& 413-E-Sales order to sales order.
Regards,
Piyush

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

Issues on cross-company stock transfer triggered by sales order

Hi, friends:
As our business process required, we need to make the cross-company sale between to plants under two company codes.
The business process required is different from standard inter-company billing in SAP SD module. Our business process is as follows:
sales order --> PR --> PO --> cross-company stock transfer --> delivery to customer --> billing.
However, there is a difficulty in this process of make-to-stock production method. When we use schedule line item in SO to trigger the PO, there is a must to assign "account assignment category" in PO. This indicator is unchangable in PO by manual. When post goods recepit against the PO, there is no stock quantity udpate in un-restricted stock. By the way, I selected "C" in the "account assignment category" of schedule line item cofiguration.
Checked the MM documents, I found it seemed like only two results of PGR against PO with account assignment category. One result of PGR is directly consumpted by receiptent or unloading point. The other result of PGR is updating sepecial stock. For example, I've fullfilled the process for make-to-order production method, the stocks are specified for sales order.
In our requiremnt, we have to post to normal un-restricted stock for the following ATP in sales order.
Could any friend give some suggestion on this issue?
Thanks!
Justin

Hi, Venkadesh:
I've checked the Purchasing view and quantity/value update in both plants of different company codes. That's correctly configured.
In the business process, the quantity in normal un-restricted stock updating still doesn't work.
Do you mean that as follows: if select any indicator in "account assignment category", we have to use UNBW or NLAG material type in the purchase order?
I have successfully fullfilled the process in make-to-order sales order, with material type FERT and account assignment category "E". The account assignmnet categroy is obligatory in sales order schedlue line item configuration, which is to trigger PO by SO. The configuration path is as below:
IMG>Sales and Distribution>Sales>Sales Documents>Schedule Lines-->Define Schedule Line Categories
If possible, would make a test in your system to check how to fullfill the process with make-to-stock sales order, FERT material?
Thanks!
Justin

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

STO for sales order stock

Hi All
If I am not mistaken, one cannot do a STO for special stock using 2 step transfer, however it is possible in a one step process.
I have made the setting in config to use a one step process, and it have been set up to use movement type 647.
I am trying to move Sales order stock from one plant to another plant, and want to maintain it as special stock.
I can get the process to create the delivery, however, when I try and post goods issue the delivery document, I get the following message.
MSSA-SABWE exceeded by 2 EA: CISCO1402 ZA30 1000 SALEABLE E
Cisco1402 is the material
ZA30 is the plant
1000 is the storage location
Saleable is the split valuation we using
E is the special stock indicator for sales order stock.
If anyone could please give me some direction.
Thanks

Hi
We are not using blocked stock at all in any of our processes.
My understanding is that movement type 647 will not look or put stock into blocked stock.
If I look at table MSSA, for that Sales order number and material number, it comes up with one entry. It has a quantity of 2 in unrestricted, Val. GR Blocked Stck is 0.
Should the quantity of 2 be appearing in there?
So the process followed thus far is:
Sales order raised
Preq auto created from SO
Preq converted to PO
GR for PO
STO created to move sales order stock from one plant to another
Delivery created,
cannot post goods issue.
Thanks

Reservation for Sales Order

Hi All,
We have a scenario with reservations in make to order:
I have a
Sale order1 for material A: 100 Kgs (Confirmed Qty)
Sale order2 for material A: 200 Kgs (Confirmed Qty)
I have created delivery document number 50kgs for sale order 1 and saved. Now when I'm trying to transfer post stock using 413 E movement type from "Sales order 1" to "Sales order 2" system is giving me an error that reservation already exists for 100Kgs. Please clarify on this:
1. How to reduce the reservation quantity so that I can transfer stock from one sale order to another?
2. Where can i see the list of reservation created for a sale order?
3. Can we stop system from creating reservations for sales order? If so what will be the effect of it?
Regards
Ayyallas

Hi,
Please 1.use MBBS report to get the reservations for sales order. 2.In OVZ9 for availability check don't include SO requirements, to avoid reservation creation for SO. 3.To reduce the stock don't create reservation against movement type(231). To reduce the quantity for sales order, its better to delete the reservation for that sales order and issue the material. For the rest of the quantity recreate the reservation for SO, if needed. If you stop reservation creation for SO, the material might not available if any immediate demand arrises. Thanking you.

FM:create a delivery for sales order in the background.

Hi experts
I want Function Module to create a delivery for sales order in the background for both inbound and outbound.
tcode : VL10A.
Thanks in advance.
kiran j

Hi Kiran,
Welcome to SDN Forums
Please use the correct or most appropriate forum.
The ABAP Objects Forum should be used for: ABAP Object definition and implementation including encapsulation, interfaces and inheritance in ABAP Objects.
This thread will be moved from to .
The forum is dedicated to: Data Transfer Techniques, Batch Data Communication, Legacy System Migration Workbench, Application Link Enabling, IDOCs, BAPIs.
Please see the [Forum Rules of Engagement|https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement] before posting.
Also read this thread Welcome and Rules of Engagement.
Greetings,
Marcelo Ramos

Error reading material cost estimate for sales order (KE292)

Dear All,
I have an issue with billing. we are posting july month transactions, the material cost is maintained through MR21. When releasing billing document for accounting we are getting error message like"Error reading the material cost estimate for sales order "11"
Message no. KE292
Diagnosis
In Profitability Analysis (CO-PA), the system tried to valuate item 000010 of sales order 11 by reading the corresponding product cost estimate.
However, no product cost estimate could be found for this sales order item.
The system accessed product costing for product AMLFP011011XX00P using costing key YB3 as defined in the
CO-PA Customizing settings.
System Response
The system cannot process the document any further.
Procedure
Check your Customizing settings."
We cross checked with other client as a current date and we ran cost estimate through CK40N with same material. and we posted entries. Here it is working fine. but in above process it is not working. Can you pls guide me where i missed.
Regards,
Nagaraju,

Hi,
When the Costing Key is assigned to the material types in the COPA customizing, then system expects Cost estimation when billing is released to Accounts.
If you dont run cost estimation but update the material master through MR21, system will not accept as in the Costing key configuration you must have selected the Current Standard price field for the valuation.
Hence, try to run cost estimation and then do releasing.
Thanks & Regards
Ravi Kumar

Error in Transfer posting for movement type 303

Hi Sir,
I am getting following error while doing Transfer posting for movement type 303 thru BAPI_GOODSMVT_CREATE
Error in Function:
Order    not found or not permitted for Goods Movement.
I am passiing all mandatory parameter for it as per BAPI Documentaion in tcode BAPI
Transfer posting
Transfer posting without reference to a reservation
The following fields must be populated:
Material number
Plant
Storage location
Movement type
Movement indicator
Quantity in unit of entry
ISO code unit of measurement for unit of entry
If I am doing manually by MB1B tcode, it is successfully done.......here its not asking any ORDER No...
Please help me .........
Regards,
Krishan

I'm not sure what you're system set up is...   So I'd suggest looking at everything you enter on the screen and then checking to make sure you are passing all the information in the BAPI.
With that said our system does require posting date, and batch. You might check that.   Also check that you've included all the required information in the header.
Did you use the same data when you tried to process the BAPI that you used when you tried to do MB1B manually?

Down Payment processing for Sales orders using Milestone Billing Plan

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

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

Store procedure for sale order

hi
i want store procedure that we can't add stand alone sale order without sale quatation

hi,
you can check my post in this link
Re: Storeprocedure for sale order without sale quotation
regards
Fidel

VD05 - Customer master record blocked for sales orders and billing

Hi,
I have a scenario whereby I have blocked a customer master record for sales orders and billing using transaction VD05, but it still allows you to create sales orders and post billing documents.
What is the reason for this?
Regards
Gandi

Hi,
Block the customer for the sales order, delivery and Billing for the specific sales area in vd05
and try out,
Regards
Pradeep BV.

Transfer posting for sale order

Similar Messages

Maybe you are looking for