COR2 -Rounding Transfer Order Quantities

Hi,
I have a following requirement.
When user changes order in COR2 and releases .Materials tab will be having quantities with 3 decimals but my user wants to round it up to a whole number in the transfer order which gets created after saving the transaction.
I need to see the changes when I run tcode LT22
I know we have userexits for COR1 but let me know if
PPCO0007 Exit when saving production order is the coreect one??
because when i kept a break-point it is not stopping.
regards
Praveen
Message was edited by:
PRAVEEN s

Similar Messages

COR2 -Rounding Transfer order Quantities -user exit

Hi,
I have a following requirement.
When user changes order in COR2 and releases .Materials tab will be having quantities with 3 decimals but my user wants to round it up to a whole number in the transfer order which gets created after saving the transaction.
I need to see the changes when I run tcode LT22
I know we have userexits for COR1 but let me know if
PPCO0007 Exit when saving production order is the coreect one??
because when i kept a break-point it is not stopping.
regards
Praveen
Message was edited by:
PRAVEEN s

Hi,
I have a following requirement.
When user changes order in COR2 and releases .Materials tab will be having quantities with 3 decimals but my user wants to round it up to a whole number in the transfer order which gets created after saving the transaction.
I need to see the changes when I run tcode LT22
I know we have userexits for COR1 but let me know if
PPCO0007 Exit when saving production order is the coreect one??
because when i kept a break-point it is not stopping.
Praveen Im having the same issue . did you find any solution for this.
Gowri

Rounding Profile for Transfer Order

Hello all,
I want to ask a question about the rounding profile for transfer order. I have a material number which has rounding profile for PO
from vendor.You can only order 60 packeges in carton.We have no problem here. The problem is after we get the order from vendor to DC we want to distribute to the store.Store create transfer order from DC with the same rounding profile.We want to transfer this item wiht the lower rounding profile from dc to store like 5 pieces minimum. If store want to create Transfer PO it has to create with 5 piece or multiple of 5.
How can I create new rounding rule for store without changing vendor rule. is that possible ?
thank you for your help..

In addition to the rounding rule in PO, you can maintain it for vendor master also. This would be specific to the vendors.
So for your store you can maintain a separate rounding rule, and create a PO. SO whenever PO is created an predefined rounding rule will get activated in the vendor master.

Transfer Order: discrepancies between GI and GR management

Hi everybody!
I'll appriciate your suggest to manage this critical scenarios:
Transfer Order from Pant A to Plant B (both the plants belong to the same company)
Case 1:
for an item GI qty is major than GE qty
For an item GI qty is less then GE qty
Case 2:
for an item the material code entered into STO and into Delivery and so registered at GI moment, is different from that effectively delivered and received at receiving plant.
Which are the necessary material documents that have to be created and so the necessary stock adjustements that have to be executed in order to solve every one discrepancies above described?
Many thanks
Roberta

Many thanks for the answers;
I'll try to explain better than before the scenarios
Case 1:
for an item GI qty is major than GE qty
--> do an addition Goods receipt for the remaining in-transit quantity.
alternative cancel the goods receipt, cancel the goods issue, redo the case with correct quantities
The case is that in the Delivery created against the STO the GI qty registered is major than that effectively receipt from the receipt plant; If I cancel the movements I've not traces if the discrepancies happened
For an item GI qty is less then GE qty
--> how can this be possible? anyhow, cancel the goods receipt and post it with the correct quantity.
alternative : cancel the goods receipt, cancel the goods issue, redo the case with correct quantities
The case is that in the Delivery created against the STO the GI qty registered is less than that effectively receipt from the receipt plant ( the whareauser has made a mistake during the picking activity); If I cancel the movements I've not traces if the discrepancies happened
Case 2:
for an item the material code entered into STO and into Delivery and so registered at GI moment, is different from that effectively delivered and received at receiving plant.
cancel the goods receipt, cancel the goods issue, redo in SAP with material that you shipped physically.
If I cancel the movements I've not traces if the discrepancies happened

WM-production order-need change the open quantity in Transfer order

Hi,
   I created the production order (order quantity 1000). i did material staging and generated TR. .
   But i need to change the open quantity in transfer order . i need to create the partial Transfer order
    against TR..
   KINDLY SUGGEST ME
   WITH REGARDS
   Dinesh

Hi Dinesh,
TO for partial qty is possible.
When you are doing material staging with 319 mov.type, you create a transfer order for partial quantity as follows:
You first create a manual transfer order using transaction LT04.
You specify the TR number in the intial screen and navigate to the detail screen, system shows the Open TR quantity and the proposed TO quantity. By default, both these quantities are equal to the TR quantity.
However, when you create by clicing the "Create TO button" (the icon with a plus sign in the tool bar of LT04 screen), system takes you to another screen where it asks for the "Requested Qty" on the top of the screen. Here you can modify the qty as per your requirement; then you can check and confirm the storage type and storage bin for source and destination stocks & save.
It is important that you give the correct source storage type & storage bin that is having stock or otherwise system might give error message.
System will create a TO line item with the entered qty and propose the balance TR qty as the 2nd TO line item. You can skip this 2nd TO item or delete it from the TO.
Once again, if you click the Save button, system will save the TO with the partial quantity.
The balance quantity will be available in the TR as open quantity and this can be seen in the header data of transaction LB03.
Regards
Prabhu

Single Transfer Order for Multiple Handling Units

I have been researchig the ability to create a single transfer order for multiple handling units. My assumptions are if it can be done that:
1) A transfer order can have a single source, so if the source document for the handling unit (delivery) is different, that means different transfer order
2) A TO can have multiple materials (line items) with different destination bins and quantities per bin
I looked at the configuration for TO Split, but it's not clear that this will handle my requirement.
I also saw this http://aq33.com/material-management/Articles-005798.html and it also says that my requirement can't be meant. I'm just checking before I tell my customer this cannot be done.

Yes you are right, if Source document is different, you need to go with different TO.
But you can choose the Handling unit split, while creating a TO itself. i.e., You can quantify the goods for each handling unit.
Edited by: Ganesh M on Feb 29, 2012 6:20 AM

Transfer Order auto create for Posting Change not working

Hello Gurus -
When we release an inspection lot from "Q" status, it creates a posting change notice, and we have it configured to create a TO in the background to the same bin, and auto confirm. The desired and intended result is to take something from "Q" status to unrestricted status, while keeping it in the same bin - and avoiding the user having to deal with the transfer orders. Essentially it is seamless and all in the background, the user just sees that he has changed something from quality status to unrestricted.
It works fine when the entire quantity is selected for the usage decision, but when a partial usage decision is made, the transfer order does not create - and requires processing in LU04 for the posting change.
Why would this work for an entire qty, but not work for a partial qty - and simply require someone to go in to LU04 and hit "create transfer order" - with no additional information?
Any help would be most appreciated. Does it have something to do with a setting of quants?

Hi,
In case of a usage decision for a partial quantity, it is not possible to create the Transfer Order for the generated posting change notice automatically. This is only possible when the full quantity is released. The same happens if you release a partial quantity and post the rest to blocked stock or scrap. The reason is, there needs to be a user decision, which part of the quantity has to be posted, this is necessary for example when the quantity is distributed in the warehouse over many storage bins. But even if the full quantity is on one storage bin, there is no automatic TO creation. You can see this also in the online
processing (LT05), in case of partial quantities you have to enter the selected quantity in the quant list, for a full posting this is not necessary.
Hope this helps,
Sinéad Curran

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

Transfer order Return

Hello everybody,
I am dealing with transfert orders return.
I created a delivery (VL10G) , posted goods issue (VL02N), and posted goods receipt on the other side (MIGO on Outbound delivery- mvt 101).
I then created a return delivery (MIGO Return Delivery against Material Document VIA Delivery) and posted goods issue (VL02N).
In MMBE, I have now my returned quantity on "StckTrsptOrderRel" on the company level.
How can I receive these quantities to get them back in the stocks of my firstly shipping (vendor) plant? What T-Code should be used?
Thanks,
Laure

Dear Laure,
Normally the process for intercompany 'return' stock transfer is as
follows:
1) Create an intercompany stock transfer order with flag 'Return'
   (transaction ME21) or an item with the return flag (field RETPO)
2) Create a delivery with VL10G
3) Create with the transaction MIGO a goods receipt from the receiving
   plant (the plant that created the NB purchase order for return -
   therfore the quantity is negativ)
   The quantity is then transferred to the transit stock.
4) Post a negative GI for the created delivery with BWART 673 which
   will transfer the quantity from transit stock to the unrestricted
   stock to the receiving plant. (the actual issuing one)
(For Intra company   Two step procedure 671
                     One step procedure 677)
5) Create a credit for it
6) and check this credit.
Please check in your business process if you follow these steps. Step
two and three can be switched but the other steps should be done in this
order. Review note 95808 for further information.
From customzing point of view:
Set delivery type for return delivery
1) IMG > MM > Purchasing > Purchase Order > Returns
   Order > Return to Vendor
2) Assign Delivery type "RL" to the appropriate supplying plants
Create a Vendor and tie it to a sold-to in the customer master
1) XK01 - create a vendor (be sure to tie it to a sold-to party in
   'Customer' field of the second screen    LFA1-KUNNR). Verify that it
   is tied to a Purchasing Organization and in the Purchasing Data
   screen select 'Returns Vendor'.
2) When the 'Return Vendor' is flagged, the system will prompt you to
   associate the vendor with an SD customer master (which you can
   create at this point). Make sure to create the customer master as a
   sold-to party, not a ship-to.
I hope this information helps!
Regards
David

ERP Delivery/Transfer Order u2013 CRM Billing

Hi everybody,
Iu2019m new to this forum and I hope that this is the right place to post my request.
Iu2019m currently developing a course in CRM and face a problem. We use an IDES client of the UCC and I try to accomplish a sales order in the CRM System, process the delivery/transportation in the ERP backend and after the delivery is completed, there should be a billing due list item created in the CRM System. The problem is, that there is no Billing Due Item created/transferred to the CRM System. Here is how the process works:
Transaction Code: CRMD_BUS2000115 bzw. CRMD_ORDER
1.     Transaction Type is Sales --> Sales Process (Item Category ZSAL)
2.     Type in the following data
   a.       Sold-to Party     300025 (01Megastore)
   b.       Product          HT-1000
   c.       Quantity          1
3.     Save the document.
4.     Go to the ERP System and check whether the sales order was transferred (Transaction Code: VA02)
5.     Create a Delivery Document (Transaction Code: VL01N). Shipping Point is 3800 (Denver) and date is
        todayu2019s date + 1 week. Save the document.
6.     Create the Transfer Order use the following settings:
a.     Warehouse number          038
b.     Plant                            3800
c.     Delivery                       the number of the delivery
d.     Foreground/Backgrnd.     System Guided
e.     Adopt Pick Quantity             2 (Include pick, quantities in delivery and post Gl)
f.     Press Enter and save.
After I create the Transfer Order the delivery should be completed and since the Item Category of the Sales Transaction Type is ZSAL and ZSAL is set to be Delivery-Related, there should be a Billing Due Item created in the CRM System. So far the theory!
Now thatu2019s where the problems begin:
1.     There is no Billing Due Item created in the CRM System
2.     I try to create a billing due in the ERP System here I get the Error message, that the u201Cgoods issue has
        not been posted for deliveryu201D
3.     I take a look at the delivery (vl02n). Here the deliveryu2019s status is still at u201Cbeing processedu201D
4.     I try to u201Cpost good issueu201D manually.
5.     I get the error message u201CSyntax Error in substitution u2018Reg_SUBu2019, step u2018001u2019u201D
The error message long text is:
Syntax error in substitution "REG_SUB", step "001"
Message no. GB032
Diagnosis
A syntax error was found in substitution REG_SUB during the ABAP code generation.
System Response
An ABAP code is not generated for this Boolean statement and the statement is evaluated as FALSE (in ABAP include GBTWMFIC).
Procedure
Correct substitution REG_SUB using substitution maintenance.
Hopefully anybody here can help me with this problem. Thanks in advance
Taymaz

Hi Stephanie,
I just wanted to point out two things:
1. As Dinesh explained already, the first scenario is mostly used if the Logistics Execution (delivery, transportation) happens in ERP, and billing was already set up and used in ERP. But in principle you can also use CRM Billing in connection with Logisitics Execution in ERP. This means you create your sales order in CRM, your delivery and so on in ERP, and then you can bill the order or the delivery in CRM. The advantage of this is that you are able to bill e.g. sales order and service order items in one invoice.
2. In the second scenario you can upload orders to ERP (if you want to do Logistics Execution), but is is not necessary (if you don't do LE). And it is not necessary and not possible to upload billing documents to ERP. CRM transfers automatically or manually the billing document to ERP FI and creates and Accounting document. So it is fully integrated without replication and without using ERP Billing.
I hope this answers your questions.
If you are interested in an integration scenarion with CRM Order - ERP Logistics Execution and CRM Billing, please watch the following short video:
[https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a07ef82a-60d2-2b10-98bb-9abcbc282bec]
Best regards,
Angela Thomas

Rounding up component quantities during Production Confirmation

Hello gurus. I have the following situation.
I have a BOM for finished product "X" that contains a component "Y" and a box "Z". The box fits 16 of these pieces. So in the BOM I type a usage quantity of .062 for component "Z" (I'm limited to 3 decimals).
Then I create a Production order for X for 32 pieces. The component overview correctly shows me requirements of 32 pieces of "Y" and 2 pieces of "Z".
The problem is; when I confirm this order in CO11N; as long as I report 32 pieces, I get a required quantity of 2 pieces for "Z", but if I want to report a partial quantity of 23 pieces, then it tells me I only need 1 piece of "Z".
I still need to use the 2 boxes but the system is rounding down to 1 piece. Only if I type 24 pieces or more, it puts it up to 2 pieces.
Is there a way to make SAP always round UP these quantities. Instead or rounding down/up depending on the quantity?

Hi Fernando,
I had the same problem.
If u keep the component quantity in fraction, the system will create more procurement proposal.
We need to keep the base quantity of the BOM header more and avoid the fraction in component qty. This will increase your accuracy when high amount of quantity requirment.
Anyway for the small amount system will do round off.
By practically also for 23 quantities you need 2 Boxes. ( as you said for 16 qtys one box).
Regards
Bala

User Exit for adjusting Transfer Order Quantity

Hi All,
We have a requirement to create a Transfer Order as soon as the production order is released. We have done the configuration for the same but we also need to adjust the Transfer Order quantity based on certain rounding value maintained in material master.
We have tried to use the exit MWMPP001 to adjust this quantity on the Transfer Order based on a field in material master. The user exit is triggered. But the target quantity is not changed as required.
We also tried using the exit MWMTO006 (Over delivery and if Necessary Under delivery Via User Exit) to adjust the TO quantity. But the exit is not being invoked.
Kindly let us know if there is any user exit or BADI to adjust the quantity in Transfer Order.
Regards,
S.Subasree

Hi Subasree,
We are facing the similar problem of user exit(EXIT_SAPLL03A_009) in the enhancement MWMTo006 is not getting invoked.
We want to use this enhancement to split the TO quantity basing on certain parameters maintained in master data. We are using Lean WM.
But, I understand from my development team, that program is checking the available stock at quant level. It will invoke the exit only if the stock available at quant is greater than the TO quantity. I didn't understand why this check is there in ECC6.0.
Currently we are using the same exit in 4.6b, where this check is not there in the code.
If you have found any solution for this(Invoking the exit) please let us know. Thankyou.
Regards
Guru

Why can't I change qty of Transfer Order

hi,guys
I had allow partially delivery goods in order, but when I created Transfer Order from delivery order, I found that I can not change pick qty in transfer order, I used LT03 to create transfer order, so, why can't I change pick qty in transfer order, it is gery!!!

Hi there,
If you want to process only a partial quantity, then you have to create delivery only for a partial quantity.
In a transfer order TO you have to pick the entire delivery quantity. Partial picking is not allowed in TO. Quantity field is blank in TO.
For eg if you have 100 items in a sales order, but you want to process only 50 now. So create a delivery for 50 items & process TO. If you create delivery for 100 items, do picking in TO for all the 100 items. Just processing TO for 50 items is not permitted. This means that all quantities in delivery has to be picked to PGI.
Regards,
Sivanand

IDOCs creation - Transfer Orders(TOs) for Deliveries - Basic doubts, thanq

Hi Experts,
Am new to IDOCs. I hv a requirement, so, request u that, Can I get some Wht to do tips from u?
My doubts:
1- I hv been asked to create IDOC, Wht does it mean?
2 - How the created IDOC will be get posted?
My requirement is:
Original inbound idoc sent from Gentran will update the delivery with all serial numbers per material for all serialized product. The message code will be the indicator that a Transfer Order-TO, idoc must be created for TO confirmation.
I need to do===>   Should be executed only when the message code on the delivery idoc is u201CTOCu201D. Look up the warehouse code on the delivery header using the delivery nbr in the delivery idoc. Create a new TO confirm idoc per delivery idoc being processed. Create a line item on this idoc for every line on the delivery idoc. Each TO line includes the delivery number and delivery item number so the TO number and line number can be looked up in table LTAP by using the delivery number and line item number found on the delivery idoc. There will be at 2 transfer orders for each delivery item b/c of the 2 step pick process, so select the TO nbr that has 916 as the destination storage type (LTAP-NLTYP). There may be more than 1 pair of TOs per delivery item so this must be completed for each TO found relevant to each delivery item.
The inbound delvry03 idoc will update the delivery with the serial numbers as part of the standard functionality. Since the transfer order must also be confirmed with the quantities on the inbound idoc, an additional idoc must be created from within the delivery update process. The transfer order can be updated and confirmed using the standard idoc and function module which should be created and initiated from the delivery update function module customer exit.
Source = DELVRY03     Destination = WMTCID01
Record Name-Field Name-Record Name-Field Name-Description---Comments
E1EDL20     VBELN-E1LTCOH-LGNUM-Warehouse Number-Look w/ idoc delivery nbr
E1EDL20     VBELN-E1LTCOH-TANUM-Transfer Order Number- Look w/ idoc delivery nbr
E1EDL24     POSNR-E1LTCOI-TAPOS-Transfer Order Line Item- Look w/ idoc delivery line nbr
EVERY THING IS DATA TRIGGERED!!!
thanq
Edited by: Srinivas on Jun 27, 2008 4:41 PM

IDOC Programming
There are two processes in IDOC processing one is INBOUND PROCESS( IDOC coming to the system and its handling at various stages) and the other is OUTBOUND PROCESS( IDOC is send to other system . Separate ABAP programs are written for these 2 processes and different configuration settings are required for each one .Depending upon the trigeering mechanism different programming approaches are used.OUTBOUND PROGRAMS handle the IDOC creation and INBOUND PROGRAMS handle the inbound IDOC and the data trasfer from the IDOC to the database tables.
NEED FOR ABAP PROGRAMMING arises if
1)New IDOC was created
Depending upon the triggering mechanism i.e change pointer,message control
etc the programming technique changes and the type of process.
2)Existing IDOC was extended
User Exits are used to populate data in new segments added and to read them
back.
3)To enhance an exsiting process.
User Exits are used .
Basic structure of an OUTBOUND PROGRAM
The basic structure of all outbound programs is same. The CONTROL
record which is of TYPE EDIDC has to be filled. It contains important fields like
IDOCTP IDOC type
MESTYP Message Type
RCVPRN Recieving Partner (Destination)
RCVPRT Partner Type (it is LS i.e Logical System)
The DATA RECORD internal table which is of TYPE EDIDD has to be filled
in the same order as there are segments in the IDOC definition.
It has 2 important fields which are to be filled ,these are
SEGNAM Name of the segment
SEGDATA Data in the segment and can be upto 1000 bytes.This field
is corresponds to each data segment in the IDOC.
e.g.
DATA INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
DATA W_SEGDATA LIKE zsegment "custom segment zsegment
INT_EDIDD-SEGNAM = 'ZSEGMENT'
W_SEGDATA-field1 = value "taken from some table
W_SEGDATA-field2 = value "taken from some table
INT_EDIDD-SEGDATA = W_SEGDATA
APPEND INT_EDIDD
This will fill the data record corresponding to the segment ZSEGMENT . For all
segments the sam steps will be repeated until all the data corresponding to all the
segments in the idoc is filled in the internal table of type EDIDD.
There is only one control record and can be multile data records in the idoc
structure.
Which data is to be extracted from the tables to be filled in EDIDD type internal table is determined in standalone programs from the objects which are specified in the selection screen and from the object key passed to the function module in case of message control and is taken from BDCP table in case of change pointers using function modules "CHANGE_POINTERS_READ"
In case of stand alone programs and function modules based on change pointers method the function module "MASTER_IDOC_DISTRIBUTE" is used to send the IDOC to ALE layer for distribution ,in case of message control it is handled automatically by the RSNASTED program invoked by the message control.
OUTBOUND PROCESS AND OUTBOUND PROGRAM.
Outbound programs are used in outbound process to genearte IDOCs . There
purpose is to extract the data from the tables and to fill the IDOC data records
and the control record in the IDOC and pass ito the ALE layer for distribution to the recieving system .
Depending upon the triggering mechanism (how and when the outbound program will be started different techniques and interface is used for outbound program.
1)Message control
Application like PO(purchase order) creation use this technique , where the output type is linked to the application(Message control is a configurable cross application component which can be set in IMG .Such programs are created in the form of function modules and linked to the output type which is linked to the apllication.These have predefined interfaces.
In outbound programs(function module) that use message control the key of the
application document is passed to the function module whcig will read the data from the table depending upon the key passed(NAST structure) and fill the IDOC segemnts with the application data.The control record is also passed to the function module but is not fully filled, the rmaining fields are filled and the control is passed back to the calling program which is RSNASTED and is invoked by the
message control to process ALE and EDI output types and this program on recieving the IDOC data will create the physical IDOC in the system.
The parameteers passed to the function module are
IMPORTING PARAMETERS
OBJECT LIKE NAST
It contains documents key.
CONTROL_RECORD_IN LIKE EDIDC
It contains the partailly filled control record
EXPORETING PARAMETER
OBJECT_TYPE
CONTROL_RECORD_OUT LIKE EDIDC
TABLES
INT_EDID LIKE EDIDD
The internal table used to fill the data records in the same order as they exists in the IDOC.
The important parameters that should be filled in the custom function module are
CONTROL_RECORD_OUT and INT_EDIDD .The OBJK field of the structue NAST contains the key of the apllication document.
2)Stand alone programs
Generally used for Master Data transfer and as such depending upon the requirement can have different interfaces.The programs have a selection screen which has select options to select the objects, and parameters for specifying the recipient Logical System and the Message Type.
Data is selected based on the specified objects from the tables . and control record of type EDIDC is created and filled with important values like DIRECTION ,IDOCTP,RCVPRT,RCVPRN and MESTYP .
Data is filled in an internal table of TYPE EDIDD according to segment definitions
and in same order and the function module MASTER_IDOC_DISTRIBUTE is called passing the control record and the internal table containg IDOC data and importing an internal table consisting of control records for each communication IDOCS created.
3)Change pointer
Change Pointer table is read and checked if changes were made to important fields , if so the outbound program will be triggered automatically , these have predefined interfaces
ALE/IDOC Transaction
SALE Area Menu for ALE configurations.It includes transactions for
Logical System definition and linking it to a client, Transactions for
RFC Destination and Port Definition Etc.
SM59 RFC Destination
Here we specify the login settings for the destination including
the I.P address or Application Server name and the User name and
password.The information entered here is used to run Remote Function
Calls(RFC ) on the destination server .We can create number of types
of RFC Destinations but 3 types are important .
R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
The name of the RFC destination should be same as that of Logical
System as it helps in creation of automatic partner profiles.
WE21 Port Definition.
There are 6 types of ports but only 2 types File and Transactional RFC
types of ports are important.
We have to specify the RFC Destination before a port can be created.
WE57 This is used to assign the Inbound function module to the Message Type
and to the IDOC Type.
WE42 This is used to define the process Code for Inbound Processing.
BD95 Define Filter object type .We can specify the field and the table it belongs
to as a filter object .
BD59 Assignment of Filter object type to the Message Type .Here we create the
link between Filter object and the segment and the message type and the
segment Field.
BD50 Set message Type to reducible.
BD65 Define Mandatory Fields.
BD64 Distribution Model . Also known as Customer Distribution Model Used to
define all the messages that will be exchanged between remote systems
and the name of thes logical systems. Any filters can also be specified.
The model once created has to be distributed on every system which will
be communicating ,It can be maintained on only One system.
BD21 Creating IDOcs from change pointers.
This can be used to create IDOCs from change pointers for a particular
message LIKE MATMAS.
BD22 This can be used to delete change pointers.
BD87 Status Monitor. Idocs can be selected base on number of criteria and there
processing status can be seen in detail.
BD10 Material Master Data Distribution .
Based on Message MATMAS.
BD12 Customer Master Data Distribution .
Based on Message CREMAS.
BD14 Vendor Master Data Distribution
Based on Message DEBMAS .
BDFG Generate ALE Interface for BAPI.
Here we specify the Business Object and the BAPI Function module for
which the interface has to be created.
WE31 Segment Editor.
This is used to create segments. We create the segment type and
segment definition is automatically created by editor e.g. Z1DUMMY is
segment type and Z2DUMMY is the segment definition .We specify the
fields and the data elements these cp\orresponds to create segments.
WE30 IDOC Editor
It is used to create a new IDOC Type or IDOC Extension .We specify the
segments that will be addd to the IDOC type.
WE02/05 IDOC List.
Various selct options and parameters are provided to select IDOCs
depending on the date, direction , mesage type etc.
WE20 Partner Profile
Here we create partner profile for each and every partner from / to which
the messages will be exchanged.There are 6 types of PF generally only
profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
We specify the partner number and partner type and the agent and
the agent type responsible for handling of errors .
For every message send to the partner we have a outbound record and for
evry message coming from the partner we have the inbound record .
We specify the message in the otbound/inbound records ,double
clicking will take us to the detailed screen where the IDOC Type ,Port
and whether the IDCO will be immediatelt processed or collected are
mentioned.

Order Quantities are accumulated with SO and SA in my own infostructure

Dear Expert,
I have problem with my own infostructure (S702) where Order Quantities are accumulated with SO and SA quantity after updating. FYI, I have done config in MC24 that some key figures such as;
Sales Document Type
Event: VA
Updating Type: B (Transfer data only)
Item Category
Event: VA
Updating Type: B
Order Quantity
Event: VA
Updating Type: A
My objective to do this that I need to segregate between SO quantity and Scheduling Agreement line quantity in that infostructure but in fact once performing SO creation, system overrides the Sales document type LP to OR and then accumulates order quantity together with SA quantity. Kindly advise.
Best regards
Mahnansa

Hi Mahnansa,
In your data structure try to define 2 different fields for Sch. agreement quantity. and sales order quantity.
In MC24 maintain
Sch Agrm. qnty with event "VB" and rule "A".
Sales ord qntry with event "VA' and rule "A" .
Rest may be the same as in Std. Info struc.
Please try, hope this should resolve.
Thanks,
Dilip S

COR2 -Rounding Transfer Order Quantities

Similar Messages

Maybe you are looking for