Related to goods movement and IDOC generation

Hi,
I need to create an IDOC for custom output type attached to transaction MIGO for purchase order after goods reciept.
How can I attach an output type with transaction MIGO.
Or is there is any other method to generate IDOC after good reciept.

Dear Goutam
All the three you can see in <b>MB51</b>.
Thanks
G. Lakshmipathi

Similar Messages

Goods Movement and Billing status at header level

Hello,
Im new to this topic and have some very basic questions
Will WBSTK field be updated with goods movement status for a given sales order number in VBUK table ?
Similarly, will FKSTK/FKSTK or BUCHK will be updated with billing status ?
I know that for a given delivery document number, I can track the status at the item level.
But my aim is to know the overall goods movement and billing status at the order header level.
Any clues will be of great help.
Thanking you in advance.
Regards,
Preethi

Hi Preethi,
A sales order does not determine a billing status for delivery related billing, field VBUK-FKSTK is only determined for delivey.
Just because of this, you will not find billing status field in VA03 -> goto header;
you could only find billing status field for delivery in VL03N -> status overview.
Best regards,
Crystal Lin

Report related to goods movement of materials?

Standard Report related to goods movement of materials?
List of goods received at individual plants
List of goods dispatched to plants
List of goods sold to customer
Please send it .

Dear Goutam
All the three you can see in <b>MB51</b>.
Thanks
G. Lakshmipathi

Good Movement Outbound Idoc

Hi ,
We have to transmit Goods movement idoc to our partner.Since i couldn't find any standard outgoing idoc for material document posting.
Therefore we are considering below two approaches to get it done
Solution 1
We will use the user exit / customer exit like MB_CF001 available at material document posting to call FMs which will populate edidc & edidd of idoc type WMMBID02 (WMMBXY message type). We will updated NAST with our hard coded output types like ZABC.As soon as the the output type gets processed the message will be transmitted to partner.(For this output type we are planning to configure despatch time as IMMEDIALTELY therefore i believe message will get transmitted as soon as material document is posted.)
But we can see few challenges in this
1) Which program and routines we have to attach with output types ?
2) In NAST along with output type we also have to update , material document number. How to get it before posting a document ?
Solution 2
We will use the user exit / customer exit like MB_CF001 available at material document posting.Using this exit we create a XML file with field and place into a disred directory. XI people will do the rest work for us.
Need you advice on the feasible solution of two and which is more cost / effort effective
regards
Shrey

Hello,
I've looked into WMMBID02 IDOC with Message type WMMBXY, and looked further into idoc documentation. It is used for inbound GR transactions. Below is what I intent to do. We issue a PO to vendor via edi, vendor ships goods to us, and using MIGO, goods receipt transaction is performed. What I intent to do is to create an outbound idoc when MIGO is performed, so that I can let the vendor know that we received the goods.
Thanks,
S

Relation of ALE , EDI and idoc

HI
     what is relation of these ALE, EDI, IDOC , i know the definition of these , i want know ( while the transfer of sap to sap ALE tool is used ,) where this idoc is used ,
regards
shivaji

Hi Shivaji,
What is EDI?
Electronic Data Interchange
     The computer-to-computer electronic exchange of machine processable business documents in a standard format
     An electronic alternative to paper, fax, and phone-based transactions used by companies to communicate with one another
Purpose:
     Allows for better time management and relieves the entering of duplicate information while cutting down on discrepancies and human intervention.
     The Electronic Data Interchange component in Sales and Distribution consists of an Intermediate Document (IDoc) [Ext.] interface. You can use this interface to
     send messages (outbound processing) such as an order confirmation through Electronic Data Interchange (EDI)
     receive messages (inbound processing) such as a sales order through EDI
EDI:
     What?
     The technology of transmitting documents electronically
     Why?
     For Electronic Data Interchange between a company and trading partners
     How?
     By means of an electronic document - the IDoc
From the SAP side, the EDI interface is based on IDoc technology, which is independent of
EDI standards. All data is transferred in files between the R/3 System and the EDI subsystem.
Synchronous Remote Function Call (RFC) is implemented to define the time of transfer for a
file between the two systems. The following data can be transferred using the EDI interface:
Outbound Idocs: IDocs are transferred from the R/3 System to the EDI subsystem.
Inbound Idocs: IDocs are transferred from the EDI subsystem to the R/3 System.
Status report: The EDI subsystem sends a status report to the R/3 System on the progress of
the processing of the outbound Idoc.
Contents of IDOC
The data in every IDoc is exchanged between the SAP system and a subsystem in the following three record types, irrespective of the IDoc type:
     Control record (Table: EDIDC): Contains information about Sender and Receiver. There is only one control record per IDoc. It consists of
IDoc Number
Sender and Receiver information
IDoc Message Type* / Port.
IDoc Type / Direction / Current status / Partner No / Partner Type (Vendor/customer)
     Data record (Table: EDIDD): Contains the message to be exchanged between Sender and Receiver. An IDoc can contain multiple data records, as defined by the IDoc structure. Data records store application data such as purchase order / sales order header information, sales order details like sales doc #, Material / Qty and other relevant information.
     Status record (Table: EDIDS): Contains Status of IDoc at various stages, during the transmission of IDoc between Sender and Receiver. Multiple status records are usually attached to an IDoc. Status records are attached to an IDoc throughout the process like status code, date and time at every stage
Know Me
Basic Type: The form of IDOC type that is originally created in the system. Like ORDERS01 is a basic type IDOC for order messages. It is using the basic types only you would be able to enhance them to suit new requirements within the same IDOC structure. Any enhancement to the basic type IDOC will produce an Extension IDOC that would be more or less similar to the basic type with some new additions (of segments or fields). Here, I would go on to say that IDOC type and Basic type is the same thing that would be referred to interchangeably.
Message type: Again, obvious from the name, its the message that is being conveyed. A message type is assigned to the Basic type. Here, logical messages are assigned to the basic type to reflect a business message being transacted. For example, ORDERS is the message type for a purchase order sent by buyer to vendor. The use of which Basic type in this message will differ from buyer to vendor. Basic types used for ORDERS are ORDERS01/02/ etc...Also, one may come up with a custom built IDOC type (or basic type as you can say)...But it is essential to associate a message type with a basic type IDOC. This feature will enable the same IDOC type to be used for a related message. For example : ORDERS01 can be used for message ORDERS for posting a order, the same IDOC can be associated with message ORDCHG to indicate that the message is an order change and so the processing of this IDOC will change accordingly.
IDoc Type:
     Defines the structure of data records
      IDoc Type is used to understand the message in string form available in the data records.
      IDoc type is version dependent i.e an Idoc type can be used only in versions in and above the version in which IDoc is released.
      Transaction WE30 is used to define and release IDoc Types
      Newly created Idoc is a BASIC IDoc and modifications
             (Additions of segments) to IDoc after it has been released can be done by creation of extension      of IDoc.
      IDoc type can be defined by structuring Segments
Function Module: The most important player in the IDOC processing. This is nothing but an ABAP program to process the IDOC. SAP has supplied function modules to process all standard basic IDOCs and messages. A function module is determined based on the Basic IDOC type and the message type (also message code). So from the above descriptions about basic and message type, the combination of two would primarily determine which IDOC will process this idoc. As an instance, ORDERS01 with message ORDERS is configured to be processed by FM IDOC_INPUT_ORDERS. Similarly, ORDERS01 + ORDCHG will be processed by IDOC_INPUT_ORDCHG. Likewise, you can see all associations in WE57 for inbound. For out bounds, you would refer to process codes (WE41).
Segments: The idenfiers in the IDOC structure which indicates the data, their level, state of occurrence....You can take them as records in the IDOC. Each individual segment will come to you as a record in the IDOC. (Go to EDID4, provide an IDOC # and it will list all included segments as records.) Segments are logically nested to indicate various levels of data (header, item etc).
Qualifiers: Inside the segments, there are fields that can carry actual data often signified by use of qualifiers. A qualifier for a segment field would provide the exact meaning of the data. For example, E1EDK03 segment is configured for dates related data. Segment field IDDAT qualifies the date type and the DATUM field gives out the actual date. So you may see a date qualified as 002, which can be interpreted as requested delivery date. Likewise you can see all qualifiers and their meanings in the associated segment fields in SE12. Give the segment name and go to the domain the ranges for the ID fields.
How EDI Works
Sending Data
     Computer system serves as a data repository.
     EDI extracts information from existing computer applications.
     Transmits paperless, computer-readable documents via telephone lines.
Receiving Data
     Fed directly into a computer system.
     Automatically processed and interfaced with internal applications.
Processing Time
     Accomplished in minutes.
     No re-keying.
     No paper shuffling.
     No attendant costs of manual document processing and delivery.
What is the difference between ALE, EDI, IDocs and BAPI?
The interface concept of the classic R/3 is based on two different strategies: Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data. The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
ALE/EDI - Purpose
Electronic Data Interchange (EDI) and Application Link Enabling (ALE) are used for exchanging business data between different systems.
For both these forms of communication, you require the IDoc Interface. The IDoc interface is made up of the definition of a data structure and the processing logic of this data structure. The data structure is the IDoc. The IDoc is the general exchange format of the communicating systems. IDocs can be sent using different methods (for example, RFC or as a file).
Application Link Enabling (ALE)
You distribute data using ALE if you want to communicate from one system to one or more other (mostly internal) systems. ALE transfers data in IDoc format and uses the methods of tRFC for data transfer.
1.     ALE enables the integration of business processes across several SAP or non-SAP systems.
Electronic Data Interchange (EDI)
You use EDI if you want to exchange business application documents with an (external) partner system (for example, a customer or vendor). The SAP system sends EDI messages in IDoc format to an EDI subsystem, where they are converted to a universal EDI standard (UN/EDIFACT or ANSI/X12). This enables communication with non-SAP systems.
1.     By definition, two partners are involved in the process in an EDI application scenario: The sender and the recipient of an EDI message.
IDoc Interface/ALE
Purpose
The IDoc interface exchanges business data with an external system.
The IDoc interface consists of the definition of a data structure, along with processing logic for this data structure.
The data structure is the IDoc. The IDoc is the exchange format common to all the communicating systems. You can specify exception handling in the SAP Business Workflow, with IDocs, without the data already having to exist as SAP application documents.
You need the IDoc interface in the following scenarios:
Electronic data exchange (EDI)
Connect other business application systems (e.g. PC applications, external Workflow tools) by IDoc
Application Link Enabling (ALE).
Application Link Enabling (ALE) is a technology to create and run distributed applications
Hope this would help you.
Reward points if helpful.
Vamsi.

SD- Related reverse goods movement

Hi,
When we are doing PGI reversal by VL09, stock is coming back to the location from it was dispatched(LM 25). Can we change the storage location so during revrse goods movement by VL09 stock will come to another storage location(LM23).

Hi Arun
It is not possible to change the storage location when you are doing the reverse goods movement in VL09
--You have done the PGI in Vl01N i.e Goods as already dispatched from this storage location.(LM25) so you cannot change the storage location as ( LM23 ) in VL09
--Once you the reverse in VL09 the goods goes back to this Storage location where it as been dispatched (LM25).
--If you want goods to be dispatched from Storage location (LM23) you have to change Storage location Vl02N before doing the PGI.
--Make sure you need to assign this storage location to your plant & maintain same Material stock in this storage (LM23).
Let me know if your problem is solved
Regards
Pradeep

Relation between goods receipt and material document number

guyz!
i got stuck up at one functional doubt. can any one say link between goods receipt and material document number. in other way, i wanted to know difference between these two i.e. goods receipt and material document number. or both are same.
awaiting for reply
manas

Hi,
Just have a look if this thread can solve ur problem.
Re: display goods receipt
Rgds,
Prakash

Idoc: post goods movement and batch classification

Hi,
I want to process a goods receipt to PO (mvt: 101) via Idoc for a batch managed part and also add some data into the batch classification.
The idoc processing works (including the creation of the classification data). but as soon as I want to add data to the classification within the same function module I get a lock entry error.
Can someone give me a hint of how to do that? what is the best option to fill additional classification data (maybe a BAPI?)
Thanks for any help!
Right now I added the following coding to the function module (copy of IDOC_INPUT_MBGMCR) which processes the idoc (here I get the error that the data of material XXX is blocked!):
    PERFORM dynpro USING:
            'X' 'SAPMM03S'     '0105',
            ' ' 'RM03S-MATNR'   batch_data-matnr,
            ' ' 'RM03S-WERKS'   batch_data-werks,
            ' ' 'RM03S-CHARG'   batch_data-batch,
            ' ' 'RM03S-LGORT'   '    ',
            'X' 'SAPMM03S'     '0200',
            ' ' 'BDC_OKCODE'   '/7',
            'X' 'SAPLCTMS'     '0109'.
    IF batch_data-trace1 NE space.
      PERFORM dynpro USING:
            ' ' 'RCTMS-MNAME(1)' 'TRACECODE1',
            ' ' 'RCTMS-MWERT(1)'   batch_data-trace1.
    ENDIF.
    IF batch_data-trace2 NE space.
      PERFORM dynpro USING:
            ' ' 'RCTMS-MNAME(2)' 'TRACECODE2',
            ' ' 'RCTMS-MWERT(2)'   batch_data-trace2.
    ENDIF.
    IF batch_data-lotno NE space.
      PERFORM dynpro USING:
            ' ' 'RCTMS-MNAME(4)' 'STM_LOT',
            ' ' 'RCTMS-MWERT(4)'   batch_data-lotno.
    ENDIF.
    IF batch_data-difflot NE space.
      PERFORM dynpro USING:
            ' ' 'RCTMS-MNAME(5)' 'STM_DIFFUSION_LOT',
            ' ' 'RCTMS-MWERT(5)'   batch_data-difflot.
    ENDIF.
    PERFORM dynpro USING:
            ' ' 'BDC_OKCODE'   '/3',
            'X' 'SAPMM03S'     '0200',
            ' ' 'BDC_OKCODE'   '/11'.
post changes
    CLEAR: msg, msg[].
    l_mode = 'N'.
    CALL TRANSACTION 'MSC2' USING tbdc MODE l_mode UPDATE 'S'
                            MESSAGES INTO msg.

Sorry! resolved it myself. I was jsut a commit missing.
I called the BAPI_TRANSACTION_COMMIT before processing my routine to update the classification data and it worked.

In which table we get the details of related to goods issue and reversal

dear experts,
hello every body please help me in finding the tables :
case 1 : when i use mb1a to issue good with movement type 531 in which table can i find the stock details .
case 2. same from 262,532.
regards,
Bh krishna mohan.

Dear
case 1 : when i use mb1a to issue good with movement type 531 in which table can i find the stock details .
case 2. same from 262,532.
SAP Tabel : Tabel will be AUFM and field BWART /MSEG
1.AUFM-MSEG for 261
2.1.AUFM-BWART for 262 , 531 , 532
Regards
JH

Goods Movement and Updation of outbound delivery.

Hi,
I am using BAPI_GOODSMVT_CREATE to do a transfer posting with movement type 411K.After doing the posting I am updating the outbound delivery for the PO using BDC recording.
The problem is that after doing the transfer posting when I try to update the outbound delivery with picked quantity and picked date it is giving an error that "Article (the article number) is blocked".Due to this the outbound delivery is not getting updated.
Could you please help me to understand why I'm getting the error and how to eliminate it? Need your help urgently.
Thanks,
Sandeep.

Hello Shashank,
Thanks for your reply.
Please let me know do these bapis mentioned by you fulfill my requirement.
Any sample code u have to use this bapis.
Regards,
Tarun

Relation between Material Movement and Material Document

Hi all,
Let me explain my doubt. I'm doing a 501 movement through Migo and through MB1C. Both create material documents, but in different ranges! :O
In Mb1c, uses the 50* range, correct
In Migo, uses the 49* range, not correct.
I can't find where is the material range - Material document relationship is done.
Can you help me?
Regards,
Pedro

Have you seen your posted documents through MIGO and MB1C in MB03.Are you able to see any document type difference once you select header.
Refer below link you will understand the process.
http://help.sap.com/saphelp_45b/helpdata/en/f8/6cec6eb435d1118b3f0060b03ca329/frameset.htm
Edited by: Sridhar Jayavarapu on Feb 10, 2010 7:01 PM

Relation between STD Price and Costing

Hi,
Could anyone explain about the relation between STD Price and Costing & when and where it gets effected.
Points will be rewarded.
Regards

Hi ,
Std. Price :-
A constant price at which a material is valuated without taking goods movements and invoices into account.
Costing:-
The value of use of economic goods both tangible and intangible for the creation and sale of goods and services, as well as the acquisition and maintenance of plant and machinery.
A process that calculates the cost of goods manufactured, or the cost of goods sold, in relation to a product or cost object.
The results of costing are used to determine the following information:
Target costs
Variances for materials produced
Contribution margin for materials sold
The costing process is based on the order quantity or the costing lot size in the material master record.
Edited by: vk on Apr 24, 2008 7:17 AM

Field disable or non editable -- goods movements

Hi team
your assistace will be highly appreciated.
I´m working with tx CO11N and after completion of the requiere data we click on goods movements button and the next screen is : "Enter production order confirmation: goods movements" and this shows some fields and what I need is to disable some of them or make them non editable : quantity, storage location and movement type.
Is it posible through Spro? if yes could you please tell the where.
I don´t want to create a variant.
thanks

I guess Variant is the only option here, atleast thats what my PP consultant had done in my last project.
There didnt seem to be any other alternative then.

Error message (M3024) during parallel goods movement

For publication distribution, collected unreferenced deliveries and goods issues are done in SAP system for a customer group by a program which is triggered by a web service every day. Standart SAP functionalities are used in this program. At goods issue part of program, an error message is occuring "Valuation data for material & is locked by the user &" with error code :M3024. The user who processes the program is locking himself. Also we have checked the other goods movement types in standart transactions (MB1B-MB11..)and same problem was occured. We have checked the notes that we applied before for to avoid material lock in paralel goods movement. There is nothing changed both in customizing and deveploment after upgrade. So we couldnt find the way to fix this problem. FIRST ANSWER FROM SAP***************************************** Can you kindly review the attached note 70865 with regards to this issue. WE APPLIED.-- We reviewed 70865 and this solution not applicable for our current system. According to note; We set material late lock exclusive time 15 seconds in OMJI. This solution solved material lock error at all plant level. After this solution, We get same batch error during goods movement(m3862), Then We applied note 157423, this note solved material batch lock error during goods movement, At last we have now m3024(Material valuation error lock) error during all goods movement. THEN********************************* As explained in the note 70865 , to ensure data integrity, it is necessary to block the material against updates by other users during good movements. This is achieved by blocking the material plant (lock object MARC) and the material valuation area (lock object MBEW) exclusively against othertransactions which update the material master. What you can do, as advised in the note, is to activate the late block via transaction OMJI. As a result of this change, several users will be able to carry out good movements to the same material and plant simultaneously. The problem is that you will experience a disadvantage of performance loss after this change. Please, notice that with this change in OMJI, several users will be ableto carry out GOODS MOVEMENTS to the same material and plant simultaneously. This change will not allow the simultaneous input of a goods movement and an invoice for the same material (in this case, the material will be locked as soon as the purchase order item is adopted in the invoice and the error message M3024 will occur). When the error message M3024 occurs, you could check with transaction SM12, there you could find some tables like MBEW are locked by user. The table is locked to prevent valuation, quantity etc. to be updated. System does not check if it is standard price or MAP, as soon as you work with one material it will be locked (its valuation data has to be locked, because otherwise there is no guarantee of the consistency of the stock values. Without this lock mechanism the possibility of serious data inconsistencies could arise). your customizing under: SPRO > IMG > Material Management > Set up Material block for goods movements Here you could choose setting 2(at positing) to have only a short locking period at posting. Please review information in attached notes. 521945 FAQ: Material block 322989 Late block: Number of blocking attempts AT LAST ** PROBLEM STILL GOING ON WHAT SHOULD WE DO TO SOLVE THIS ERROR.

HI Fatih,
Refer to SAP Note 1744780 - Error message M3024 during Invoice Verification process .
In the standard system it is not possible the simultaneous entry of a GOODS MOVEMENTS and an INVOICE for the same material and the same plant.
When you enter the invoice for the purchase order item, the valuation data for the material is updated, therefore this valuation data (table MBEW) needs to be blocked so that it is not changed at the same time by any other transaction (which might cause inconsistencies).
Resolution
This system behavior can not be avoided by any customizing setting or any user exit.
This is correct system behavior to protect the other transactions update the material master.
As advised in the note 70865 :
It is possible to activate the late block via transaction OMJI. As a result of this change, several users will be able to carry out good movements to the same material and plant simultaneously, however there is a risk to cause the data inconsistency and performance problems.

EDI message output for goods movements

Dear experts,
we configured NACE to send EDI messages, when goods movements are created. When we use partner type "VN" (Vendor) and leave the partner number empty, no message is created. Only if the partner number is filled, a message is created. This means, that the partner number is not extracted dynamically from the goods movement and we have to make one NACE entry for each partner. For other applications (e. g. outbound call offs), the partner number in NACE can be left empty and when a document is posted, the receiver partner number is determined dynamically.
Is it possible to modify the processing, so that the partner number is extracted from the goods movement? How can this be done?
Best regards,
David Claes

Hi,
What is the application you selecting for creating ouput?
I don't see output record condition with as combination.
You should be using ME as application area.
Thank you!
Dipak

Related to goods movement and IDOC generation

Similar Messages

Maybe you are looking for