OBDLV_PROCOUTP01 (inbound // outbound processing)

Hi,
Does anybody know the exact function of this IDOC?
I can only find the inbound processing function.
Is there also an outbound function?
Thanks
Ron

Hi ram,
have you had a look into tRFC Queue of your sending system? Although an IDoc is in Status 03 it may not be sent due to network errors etc.. In that case the IDoc will be still in the tRFC Queue (SM58).
did you test the rfc connection from tcode SM59? Use authorization from test menu or remote logon button. Test connection does - as far as I know - only a ping like test (ensuring the system is there but not the client).
tcode SMGW might helpful but I used it very rarely only.
goto WE02/WE05 transaction also may help.
check ALE configuration is perfect?
regards,
San!
If helped,do assign points.

Similar Messages

Inbound & outbound process

Hi All,
I am new to ALE. I want to know what is the actual process behid inboud and outbound services in ALE.

Hi,
1.Here out bound means sender.Inbound mens --receiver.
Data Creation in Idoc
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.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
There are two filtering in IDoc.
Segment Filtering:
Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.
Data Filtering:
Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
Please check this link for more information.
http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
Regards,
Shiva.

What is IDOC Inbound process and Outbound Process?

What is IDOC Inbound process and Outbound Process?
can any one explain about the inbound and outbound process step by step?
Tks in advance,
Phanikumar

Hi,
Inbound means transfer legacy data to SAP system and
outbound means transfer SAP system data to legacy system.
Regards,
Prashant

IDod Type,Message Type,Inbound Function,Process Code Required

Dear All,
I require
1. IDoc Type
2. Message Type
3. Inbound Function
4. Process Code
for
a. Vendor Master Creation,Updation,Deletion
b. Customer Master Creation,Updation,Deletion
c. Vendor Invoice(TCode-FB60) Creation,Updation,Creation
d. Vendor Credit Memo(Tcode-FB65) Creation,Updation,Creation
e. Customer Invoice(TCode-FB70) Creation,Updation,Creation
f. Customer Credit Memo(TCode-FB75) Creation,Updation,Creation
i require to insert all the above detail into SAP from another system so please provide me the full detail.if the IDoc type is separate for Creation Updation Deletion then provide likewise.
Everybody will rewarded.
Thanks,
RP

hi
use t code wedi and goto EDI administration menu. in that goto development menu. there you can find all items like Idoc type, message type or process code all information is available. You can also use t code WE30,WE31,WE80,WE81, WE42 - Inbound process code and WE41 Outbound process code.
Hope this helps. Assign points if useful.
Rago

How to know whether we are in Inbound Idoc processing ?

Hi,
Can we know from any system variables that whether we are in Inbound Idoc processing?
Rgds,
Antony

Hi Antony,
Inbound or Outbound is clssified based on Direction Filed.
If we have IDOC Number chk in EDIDC its direction
If Direct = 1(Outbound) or =2 (Inbound) i think
Regards,
Poornima

Setting in ERP system required: replicate Inbound/Outbound delivery to EWM

Hi Experts.
I have done all primary Configuration Settings for the ERP System and EWM system (using SPM setting, bcez its is ecc 6.0 sr2 ench pack 2 or 3)
Suppose, plant is 0001, storage location 0001 is mapped to warehouse number EW1 in ERP
Warehouse numbers are mapped ERP (EW1) and EWM system (EWM1)
ERP system. For Inbound delivery processing in VL60
1)My question how to configure new Vendor with receiving point should be< EWM1> and warehouse number should be <EW1> ( to replicated inbound delivery in EWM SYSTEM )
For outbound setting for VL01N.
2) How to configure
Shipping to <EWM1>
Delivery type & Sales area ( sales org, Distribution channel , division ) .let me know any configuration required for delivery type & sale area. ( to replicated outbound delivery in EWM SYSTEM).
Waiting for your reply .
Thankyou

ERP system. For Inbound delivery processing in VL60
1)My question how to configure new Vendor with receiving point should be< EWM1> and warehouse number should be <EW1> ( to replicated inbound delivery in EWM SYSTEM )
There is no relation between a vendor and the receiving point. Actually, you may not require a 'receiving point' to be able to transmit the ECC inbound delvy to EWM. The setting that will drive is the assignment of ECC 'dummy' Warehouse to Plant/storage location and the assignment of this ECC 'dummy' warehouse to EWM Warehouse, in ECC. Similar setting is to be made in EWM where the assignment of business system is made with ECC dummy warehouse and EWM warehouse, in EWM.
In addition to this, you'll need to have the mapping of ERP document type to EWM document type along with the mapping ot ERP item category to EWM item type.
For outbound setting for VL01N.
2) How to configure
Shipping to <EWM1>
Delivery type & Sales area ( sales org, Distribution channel , division ) .let me know any configuration required for delivery type & sale area. ( to replicated outbound delivery in EWM SYSTEM).
The above note is the same for this as well.

ALE/Idoc (inbound & outbound)

Hi,
Can any one help me by providing simple sample code for creation of ALE/Idoc (inbound & outbound). Where I need do understand flow cycling of outbound from one client to other inbound client. Waiting for replay. My email-ID is [email protected]
Regards,
Lokesh.K

Hi,
have you seen these documentation sections?
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/78/2174b051ce11d189570000e829fbbd/frameset.htm">Implementing Inbound Processing</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/78/2177bc51ce11d189570000e829fbbd/frameset.htm">Implementing Outbound Processing</a>
Hope they'll help.

Outbound process code for MBGMCR02

Hello Experts:
    I need to send out material movement (document) information using IDOC. I found MBGMCR02 is a suitable one but the process code is inbound.
    I read some thread, it said you can create a new outbound process code. But I don't know exactly how to do it.
    Can anyone share some advice?
    Thanks a lot.
Dennis

Hi Dennis,
To solve this problem create the outbound process code using the following method:
Goto txn WE41 : Create a new outbound process code say ZMMGRO and assign your message type MBGMCR to this.
Also maintain a FM say ZMBGMCR_IDOC_OUPUT which process the IDOC in the outbound side.
The FM signature should typically look like this:
""Local Interface:
*" IMPORTING
*"     VALUE(OBJECT) LIKE NAST STRUCTURE NAST
*"     VALUE(CONTROL_RECORD_IN) LIKE EDIDC STRUCTURE EDIDC
*" EXPORTING
*"     VALUE(OBJECT_TYPE) LIKE WFAS1-ASGTP
*"     VALUE(CONTROL_RECORD_OUT) LIKE EDIDC STRUCTURE EDIDC
*" TABLES
*"      INT_EDIDD STRUCTURE EDIDD
*" EXCEPTIONS
*"      ERROR_MESSAGE_RECEIVED
*"      DATA_NOT_RELEVANT_FOR_SENDING
TABLES: MKPF, MSEG.
data wa_mkpf type MKPF.
data it_mseg type TABLE OF MSEG.
data wa_mseg like LINE OF it_mseg.
data wa_E1BP2017_GM_HEAD_01 type E1BP2017_GM_HEAD_01.
data wa_E1MBGMCR type E1MBGMCR .
data wa_E1BP2017_GM_ITEM_CREATE type E1BP2017_GM_ITEM_CREATE.
data wa_E1BP2017_GM_CODE type E1BP2017_GM_CODE.
data wa_E1BP2017_GM_ITEM_CREATE1 type E1BP2017_GM_ITEM_CREATE1.
data wa_E1BP2017_GM_SERIALNUMBER type E1BP2017_GM_SERIALNUMBER.
data wa_edidd type edidd.
Create Control Record **********
move CONTROL_RECORD_IN to CONTROL_RECORD_OUT.
control_record_out-direct = '1'.
control_record_out-serial = sy-datum.
control_record_out-serial+8 = sy-uzeit.
Fill Segment data from MKPF & MSEG ******
clear wa_edidd.
clear wa_E1MBGMCR.
move wa_E1MBGMCR to wa_edidd-sdata.
wa_edidd-segnam = 'E1MBGMCR'.
append wa_edidd to int_edidd.
Select single * from MKPF into wa_mkpf where
mblnr eq OBJECT-OBJKY+0(10)
and mjahr eq OBJECT-OBJKY+10(4).
clear wa_edidd.
clear wa_E1BP2017_GM_HEAD_01.
wa_E1BP2017_GM_HEAD_01-PSTNG_DATE = wa_mkpf-BUDAT.
wa_E1BP2017_GM_HEAD_01-DOC_DATE = wa_mkpf-BLDAT.
wa_E1BP2017_GM_HEAD_01-BILL_OF_LADING = wa_mkpf-FRBNR.
wa_E1BP2017_GM_HEAD_01-PR_UNAME = wa_mkpf-USNAM.
wa_E1BP2017_GM_HEAD_01-HEADER_TXT = wa_mkpf-BKTXT.
move wa_E1BP2017_GM_HEAD_01 to wa_edidd-sdata.
wa_edidd-segnam = 'E1BP2017_GM_HEAD_01'.
append wa_edidd to int_edidd.
SELECT * from mseg INTO TABLE it_mseg where
mblnr eq OBJECT-OBJKY+0(10)
and mjahr eq OBJECT-OBJKY+10(4).
loop at it_mseg into wa_mseg.
CLEAR wa_edidd.
CLEAR wa_E1BP2017_GM_ITEM_CREATE.
wa_E1BP2017_GM_ITEM_CREATE-MATERIAL = wa_mseg-MATNR.
wa_E1BP2017_GM_ITEM_CREATE-PLANT = wa_mseg-WERKS.
wa_E1BP2017_GM_ITEM_CREATE-STGE_LOC = wa_mseg-LGORT.
wa_E1BP2017_GM_ITEM_CREATE-BATCH = wa_mseg-CHARG.
wa_E1BP2017_GM_ITEM_CREATE-MOVE_TYPE = wa_mseg-BWART.
wa_E1BP2017_GM_ITEM_CREATE-STCK_TYPE = wa_mseg-INSMK.
wa_E1BP2017_GM_ITEM_CREATE-SPEC_STOCK = wa_mseg-SOBKZ.
wa_E1BP2017_GM_ITEM_CREATE-VENDOR = wa_mseg-LIFNR.
wa_E1BP2017_GM_ITEM_CREATE-ENTRY_QNT = wa_mseg-MENGE.
wa_E1BP2017_GM_ITEM_CREATE-ENTRY_UOM = wa_mseg-ERFME.
wa_E1BP2017_GM_ITEM_CREATE-PO_NUMBER = wa_mseg-EBELN.
wa_E1BP2017_GM_ITEM_CREATE-PO_ITEM = wa_mseg-EBELP.
move wa_E1BP2017_GM_ITEM_CREATE to wa_edidd-sdata.
wa_edidd-segnam = 'E1BP2017_GM_ITEM_CREATE'.
append wa_edidd to int_edidd.
endloop.
ENDFUNCTION.
Do remember to maintain the message control in WE20 where you maintain this outbound code against your output type.
Hope this helps!

Movement types corrsponds to Inbound ,Outbound and Internal transaction

Hi,
Can anyone tell me the list of movement types corresponding to the Inbound,Outbound and for Internal Transaction.
for example: movement type 101 corresponds to Inbound transaction.
Thanks

Dear Bala,
This may help you.....
Below you will find a short description of the standard movement types. The cancellation movement type is the movement type + 1 (cancellation for 101 = 102).
101 Goods receipt for purchase order or order
If the purchase order or order has not been assigned to an account, a stock type (unrestricted-use stock, stock in quality inspection, blocked stock) can be entered during goods receipt.
If the purchase order or order has been assigned to an account, the goods receipt is not posted to the warehouse, but to consumption.
In the case of non-valuated materials, the goods receipt is posted to the warehouse, although the purchase order has not been assigned to an account.
Possible special stock indicators:
o     K Goods receipt for purchase order to consignment stock
o     O Goods receipt for purchase order to stock of material provided to vendor
o     E GR for purchase order or order to
o     sales order stock
o     Q GR for purchase order or order to
o     project stock.
Goods receipt for subcontract order : at goods receipt, the consumption of the components is posted at the same time (see movement type 543)
Goods receipt for
stock transport order : at goods receipt the transported quantity is posted in the receiving plant from stock in transit into unrestricted-use stock (or stock in quality inspection, blocked stock).
103 Goods receipt for purchase order into GR blocked stock
The GR blocked stock is not valuated.
You cannot receive goods into GR blocked stock for stock transport orders.
105 Release from GR blocked stock for purchase order
Movement type 105 has the same effects as 101.
121 Subsequent adjustment for subcontracting
This movement type cannot be entered manually.
With a subsequent adjustment for a subcontract order it is possible to correct the consumption of components. In this case, the material produced by the supplier is credited with the excess consumption / under-consumption. For this reason, if there is a subsequent adjustment, an item is generated for the produced material using movement movement type 121.
Movement type 121 does not have a reversal movement type.
122 Return delivery to supplier or to production
Using movement type 122, you can distinguish real return deliveries for a purchase order or order from cancellations (102).
In the standard version, you must enter a reason for the return delivery if you are using movement type 122. In this way, evaluations of return deliveries are possible.
The effects of movement type 122 correspond to a cancellation of movement type 101.
123 Reversal of return delivery
If you returned a goods receipt using movement type 122, you can reverse the return delivery using movement type 123.
Movement type 123 has the same effects as movement type 101.
124 Return delivery to vendor from GR blocked stock
Using movement type 124, you can return a goods receipt to GR blocked stock (103).
Movement type 124 has the same effects as movement type 104.
125 Return delivery from GR blocked stock - reversal
If you returned a goods receipt to GR blocked stock using movement type 124, you can reverse the return delivery using movement type 125.
Movement type 125 has the same effects as movement type 103.
131 Goods receipt for run schedule header
This movement cannot be entered manually. It is generated automatically at notification of goods receipt for a run schedule header.
Possible special stock indicators: E und Q
161 Return for purchase order
If a purchase order item is marked as a returns item, the returns to vendor are posted using movement type 161 when the goods receipt for purchase order is posted.
Movement type 161 has the same effects as movement type 122.
201 Goods receipt for a cost center
The goods can only be withdrawn from unrestricted-use stock.
Possible special stock indicators:
o     K: Goods withdrawal from
o     consignment stock
o     P: Goods withdrawal from pipeline
If you have withdrawals from consignment stock and from pipeline, payables to suppliers ensue.
221 Goods issue for a project
The goods can only be withdrawn from unrestricted-use stock.
Possible special stock indicators: K, Q
231 Goods issue for a customer order (without SD)
You use this movement type if you want to process the delivery without SD.
The goods can only be withdrawn from unrestricted-use stock.
Possible special stock indicators: E, K, Q
241 Goods issue for an asset
The goods can only be withdrawn from unrestricted-use stock.
Special stock indicator: K
251 Goods issue for sales (without customer order)
Use this movement type if you have not entered a customer order in SD. In the standard system, the movement is assigned to a cost center. kontiert.
The goods can only be withdrawn from unrestricted-use stock.
Possible special stock indicators: K
261 Goods issue for an order
This refers to all withdrawals for orders (for example, production order, maintenance order, except customer orders.
Possible special stock indicators: E, K, P, Q, W
The goods issue can be posted manually in Inventory Management or automatically when an order is confirmed or via an SD delivery.
281 Goods issue for a network
The goods can only be withdrawn from unrestricted-use stock.
Possible special stock indicators: E, K, P, Q
The goods issue can also be posted via an SD delivery.
291 Goods issue for any arbitrary account assignment
With this movement type, all account assignment fields are ready for input. You can assign the movement to an arbitrary account assignment object.
The goods can only be withdrawn from unrestricted-use stock.
Possible special stock indicators: E, K, P, Q
301 Transfer posting plant to plant in one step
The quantity is transferred from unrestricted-use stock in the issuing plant to unrestricted-use stock in the receiving plant.
Possible special stock indicators: O, V, W
303 Transfer posting plant to plant in two steps - removal from storage
The quantity is transferred from unrestricted-use stock of the issuing plant to stock in transfer in the receiving plant.
For technical reasons, you cannot carry out transfer postings from plant to plant in two steps for split-valuation materials.
Removal from storage can be posted via an SD delivery.
305 Transfer posting plant to plant in two steps - placement in storage
The quantity is posted from
stock in transfer to unrestricted-use stock in the receiving plant. The movement is not valuated.
You can enter the goods receipt with reference to the SD delivery.
309 Transfer posting material to material
The quantity is posted from unrestricted-use stock of the issuing material into unrestricted-use stock in the receiving material
Prerequisite: both materials have the same stockkeeping unit.
Possible special stock indicators: E, O, Q, V, W
311 Transfer posting storage location to storage location in one step
The quantity is transferred from unrestricted-use stock of the issuing storage location to unrestricted use in the receiving storage location.
Possible special stock indicators: E, K, M, Q
See also 321, 343, 349, 455 for other stock types.
313 Stock transfer storage location to storage location in two steps - removal from storage
The quantity is transferred from unrestricted-use stock of the issuing storage location to stock in transfer in the receiving storage location.
315 Transfer posting storage location to storage location in two steps - placement in storage
The quantity is transferred from the
stock in transfer to the unrestricted-use stock in the receiving storage location.
317 Creation of a structured material from constituent components (Retail)
A material split into its components using movement type 319 can be rejoined using movement type 317.
Movement type 317 has the same effect as a cancellation of movement type 319.
319 Split structured material into components (Retail)
You can enter the splitting of a structured material manually using movement type 319.
You can configure Customizing so that a structured material (for example, (z.B. set, prepack or display) is automatically split into its components at goods receipt. The system posts the split using movement type 319. In this process, the BOM header material is posted and each of the component stocks are increased. You can also use this function if you use the Warehouse Management System (WM).
Example:
A box of the structured material S contains 3 pieces of the component K1 and 4 pieces of the component K2. The following material document items result after the material is split at goods receipt:
     Qty      Unit      Material      Movement type
     1      box      S      101 +
     1      box      S      319 -
     4      piece      K1      319 +
     5      piece      K2      319 +
321 Transfer posting stock in quality inspection - unrestricted-use stock
The quantity is transferred from stock in quality inspection into unrestricted-use stock. Here it is possible to post the quantity to another storage location.
This movement type is not possible for QM-managed materials since the transfer posting for these materials takes place using the usage decision.
Possible special stock indicators: E, K, O, Q, V, W
323 Transfer posting storage location to storage location - stock in quality inspection
The quantity is transferred from stock in quality inspection in the issuing storage location into stock in quality inspection in the receiving storage location.
Mögliche Sonderbestandskennzeichen: E, K, Q
325 Transfer posting storage location to storage location - blocked stock
The quantity is transferred from blocked stock in the issuing storage location into blocked stock in the receiving storage location.
Possible special stock indicators: E, K, Q
331 Withdrawal of sample from stock in quality inspection
333 Withdrawal of sample from unrestricted-use stock
335 Withdrawal of sample from blocked stock
The sample is destructive, that is, the withdrawal has the same effects as scrapping.
Possible special stock indicators: E, K, Q, V, W
341 Change in status of a batch (available to not available)
This goods movement is automatically created when there is a change in the status of a batch and it is also used to transfer the unrestricted-use stock into restricted-use stock.
Possible special stock indicators: E, K, M, O, Q, V, W
343 Transfer posting blocked stock - unrestricted-use stock
349 Transfer posting blocked stock - stock in quality inspection
The quantity is transferred from blocked stock to unrestricted-use stock (343) or stock in quality inspection (349).
Here it is possible to transfer the quantity to another storage location.
Possible special stock indicators: E, K, Q
351 Goods issue for a stock transport order (without SD)
The quantity is transferred from unrestricted-use stock in the issuing plant to stock in transit in the receiving plant.
Movement type 351 is only used if the goods issue is posted without an SD delivery. A goods issue for a stock transport order with SD delivery is posted using movement type 641 or 643.
The transfer posting is also possible for materials valuated separately.
The goods issue for a stock transport order takes place using movement type 101.
Possible special stock indicators: E, Q
For special stock indicators E and Q and for purchase orders assigned to an account, ensure that the quantity is not posted to the stock in transit in the receiving plant.
401 Transfer of sales order stock into company's own stock
(no longer available as of Release 4.0C)
The quantity is transferred from unrestricted-use sales order stock (non-valuated) into unrestricted-use storage location stock (valuated). For this movement, a special stock indicator is not required.
It is possible to change the material number using this movement - if the material is managed in the company's own stock under a different material number (for example, for materials that can be configured).
403 Transfer of consignment stock to company's own stock
(no longer available as of Release 4.0C)
The quantity is transferred from unrestricted-use consignment stock into unrestricted-use storage location stock and thus taken into the valuated stock. This results in a payable for vendors. For this movement, a special stock indicator is not required.
405 Transfer of project stock to company's own stock
(no longer available as of Release 4.0C)
The quantity is transferred from unrestricted-use project stock to unrestricted-use storage location stock. A special stock indicator is not required for this movement.
411 Transfer of special stocks E, K, and Q to company's own stock
The quantity is transferred from unrestricted-use special stock E ( sales order stock ), unrestricted-use special stock K ( consignment stock) and unrestricted-use special stock Q ( project_stock ) to unrestricted-use storage location stock. The corresponding special stock indicator is required for this movement.
If you do not use the special stock indicator, the system uses this movement type and movement type 311.
For sales order stock, you can change the material number for this movement if you manage the material in your company's own stock under a different material number (for example, for configurable materials).
Consignment stock is transferred to valuated stock, thus resulting in a vendor liability.
441 Transfer posting non-tied to tied empties
Part of the stock of an "empties" material assigned to a full product is managed in the stock type "tied empties".
Empties stock not assigned to a full product forms part of the stock type "unrestricted-use".
Using movement type 441, you can make a transfer posting for an empties material from the stock type "unrestricted-use" to the stock type "tied empties". Movement type 442 reverses this transaction.
Example:
The full product "beer" has a stock of 15 cases. Part of the empties components "bottle" and "case" is tied empties stock.
     Material      unrestricted-use      tied empties
     Beer      15
     Bottle      240      360
     case      10      15
451 Returns from customers (without SD)
Using movement type 451, you post customer returns without an SD returns delivery into blocked stock returns . The blocked stock returns are not valuated.
No special stock indicator possible.
See also 453, 651, 653
453 Transfer posting blocked stock returns to unrestricted-use stock
457 Transfer posting blocked stock returns to quality inspection stock
459 Transfer posting blocked stock returns to blocked stock
The quantity is transferred from blocked stock returns to unrestricted-use stock (453), quality inspection stock (457) or blocked stock (459) and thereby transferred to valuated stock.
With this movement you can transfer the quantity to another storage location at the same time.
455 Transfer posting storage location to storage location - blocked stock returns
The quantity is transferred from blocked stock returns of the issuing storage location to blocked stock returns of the receiving storage location.
501 Goods receipt without purchase order - unrestricted-use stock
503 Goods receipt without purchase order - stock in qual.inspection
505 Goods receipt without purchase order - blocked stock
These movement types are used for deliveries from vendors that are not based on a purchase order. Invoice verification is not possible for these goods receipts.
Mögliche Sonderbestandskennzeichen: E, K, M, Q
Bei einem Wareneingang zur Bestellung (101) kann der Zugang von
Mehrwegtransportverpackung als zusätzliche Position mit 501 und Sonderbestandskennzeichen M erfaßt werden.
511 Free-of-charge delivery from vendor
The quantity is posted to unrestricted-use stock. If there is a material with moving average price, the moving average price is reduced accordingly.
521 Goods receipt without order - unrestricted-use stock
523 Goods receipt without order - stock in quality inspection
525 Goods receipt without order - blocked stock
The movement types are used for deliveries from production that are not based on a delivery.
Possible special stock indicators: E, Q
531 Goods receipt from by-product from the order
The goods receipt of a by-product usually refers to an order, but it can be entered without a reference.
If a component is entered with a negative quantity in the order, a reservation item is created with 531 (instead of 261). The receipt of a by-product can be entered when the component for the order is withdrawn from stock or it can be entered as another type of goods receipt.
Possible special stock indicator: E, Q
See also: 545 and 581
541 Transfer posting unrestricted-use stock - stock of material provided to vendor
WIth the movement type you provide the subcontractor with the components required for subcontract orders . The quantity is posted into unrestricted-use stock of material provided to vendor.
If there is a goods receipt for a subcontract order (101), the consumption of components is posted from this stock.
Special stock indicator cannot be used.
The transfer posting can be posted via an SD delivery.
543 Consumption from stock of material provided to vendor
This movement cannot be entered manually.
The consumption of components for a subcontract order is posted using goods receipt for purchase order (101). It can be corrected by means of a subsequent adjustment.
Possible special stock indicators: E, Q.
For the special stock indicators E and Q, you must ensure that the quantity is not removed from the stock of material provided to vendor, but from the unrestricted-use sales order or project stock.
545 Goods receipt from by-product from subcontracting
If a component is entered with a negative quantity for the subcontract order, the receipt of the by-product is posted during goods receipt for purchase order or during the subsequent adjustment.
Possible special stock indicators: E, Q
For special stock indicators E and Q, you must ensure that the quantity is not posted to the stock of material provided to vendor, but to the unrestricted-use sales order or project stock.
551 Scrapping from unrestricted-use stock
553 Scrapping from stock in quality inspection
555 Scrapping from blocked stock
Possible special stock indicators: E, K, Q
561 Initial entry of stock - unrestricted-use stock
563 Initial entry of stock - quality inspection
564 Initial entry of stock - blocked stock
During initial entry of stock balances, you enter the physical warehouse stock frigures or the book inventory from your old system into the SAP System for productive operation. This data entry usually takes place by means of batch input.
Possible special stock indicators: E, K, M, O, Q, V, W (565: only E, K, Q)
571 Goods receipt for assembly order to unrestricted-use
573 Goods receipt for assembly order to quality inspection
575 Goods receipt for assembly order to blocked stock
This movement cannot be entered in Inventory Management, but only in repetitive manufacturing using the function "Goods receipt for sales order".
Possible special stock indicators: E, K, Q
581 Goods receipt of a by-product from the network
The goods receipt of a by-product usually refers to a network , but can be entered without reference.
If a component is entered with a negative quantity in the network, a reservation is created with 581 (instead of 261). The receipt of a by-product can be entered during the withdrawal for the network or as another type of goods receipt.
Possible special stock indicators: E, Q
601 Goods issue for delivery (SD)
This movement cannot be entered manually. It is created automatically in SD using the function "Goods issue for delivery".
The quantity is taken from unrestricted-use stock.
Possible special stock indicators: E, K, Q
621 Transfer posting unrestricted-use - returnable packaging (SD)
This movement is generated by SD.
The quantity is transferred from unrestricted-use stock to the returnable packaging stock at customer .
623 Goods issue from returnable packaging stock at customer(SD)
This movement is generated by SD.
This quantity is withdrawn from unrestricted-use returnable packaging stock at the customer.
631 Transfer posting unrestricted use - customer consignment stock (SD)
This movement is generated by SD.
The quantity is transferred from unrestricted-use stock to consignment stock at customer.
633 Goods issue from customer consignment (SD)
This movement is generated by SD.
The quantity is withdrawn from unrestricted-use consignment stock at the customer.
641 Goods issue for a stock transport order (SD)
This movement is generated by SD.
The quantity is transferred using an SD delivery from unrestricted-use stock of the issuing plant to stock in transit of the receiving plant.
The goods receipt for the
stock transport order takes place using movement type 101 and can, if required, refer to the purchase order or to the delivery.
Possible special stock indicators: E, Q
For the special stock indicators E and Q and for purchase orders assigned to an account, you must ensure that the quantity is not posted to the stock in transit of the receiving plant.
See also: 351, 643
643 Goods issue for a cross-company stock transport order (SD)
This movement is generated by SD.
It is used only for cross-company stock transport orders with SD billing and invoice. The quantity is withdrawn from the unrestricted-use stock of the issuing plant. No stock in transit is created here. In the second step, the goods receipt must be entered.
Siehe auch: 351, 641
645 Goods issue for a cross-company stock transport order in one step
(SD)
This movement is generated by SD.
Unlike movement type 643, when a goods issue is posted using movement type 645, a goods receipt line is generated automatically.
647 Goods issue for a stock transport order in one step (SD)
This movement is generated by SD.
Unlike movement type 641, when a goods issue is posted using movement type 647, a goods receipt line (101) is generated automatically.
651 Returns from customer (SD)
This movement is generated by SD.
Using movement type 651, you post returns from a customer with the SD returns delivery to blocked stock returns . The blocked stock returns are not valuated.
Special stock indicators not possible.
See also: 451, 453, 653
653 Returns from customer (SD) to unrestricted-use stock
655 Returns from customer (SD) to stock in quality inspection
657 Returns from customer (SD) to blocked stock
These movements are generated by SD.
With these movement types you post returns from the customer with SD returns delivery directly to the valuated stock.
Possible special stock indicator: E
See also: 451, 453, 651
661 Returns to vendor via SD delivery
As with movement type 502, a return delivery to the vendor is entered without reference to the purchase order, but the goods issue is posted via an SD delivery.
671 Returns for stock transport order via SD delivery
If a purchase order item is marked as a returns item, when a goods receipt for a stock transport order (101) is posted, the return is posted to stock in transit using movement type 161. When the return arrives, the issuing plant posts the goods receipt for the return using movement type 671. Movement type 671 (like movement types 352 and 642) reduces the receiving plant's stock in transit and increases the the issuing plant's unrestricted-use stock.
701 through 708: Inventory differences in MM
These movements are generated automatically during inventory difference posting in Inventory Management.
711 through 718: Inventory differences in MM-WM
These movements are generated when you post the inventory differences from Warehouse Management to Inventory Management.
721 - Sales value receipt - not affecting margins (Retail)
The movement is generated automatically when the sales price of a value-only material is changed (total sales price revaluation on the posting date).
731 - Sales value receipt - affecting margins (Retail)
The movement is generated automatically when the sales price of a value-only material is changed (partial sales price revaluation on the posting date).
Regards
Ravi

Inbound outbound email check in R12

Hi gurus:
We installed 12.1.3 EBS with 11.1.0.7 dabase on Linux. The workflow and every thing is good now. I want to check inbound and outbound email works good or not every day. How do I do that?
Thanks and regards

You need to check MAIL_STATUS AND STATUS columns. For details about these columns, please see:
Why Notifications in WF_NOTIFICATIONS have mail_status NULL and Status OPEN [ID 1549691.1]
What to Review When Notifications are not Emailed (Outbound Processing)? [ID 1051421.1]
http://etrm.oracle.com/pls/et1211d9/etrm_pnav.show_object?c_name=WF_NOTIFICATIONS&c_owner=APPLSYS&c_type=TABLE
Thanks,
Hussein

Inbound/Outbound delivery

Hi all,
Can anybody explain about inbound delivery and outbound delivery.... please provide any URL if available.
Thnks & regards
SAP Beginner

Hi,
the inbound delivery supports all activities such as putaway, packing, transportation and goods receipt. During the inbound delivery process, planning information is recorded, the status of different activities is monitored, and data accumulated during inbound shipment processing is documented. When the inbound delivery is created, activities such as putaway or scheduling are initiated, and data that is generated during processing of the inbound delivery is included in the delivery.
From PO we can make inbound delivery via :
1. EDI
2. Collective processing
3. Manually...
For outbound del. use the link:
Inbound delivery
Hope it helps...
Regards,
Priyanka.P
updating..
Edited by: Priyanka Paltanwale on Sep 26, 2008 1:45 PM

Transaction codes for inbound/outbound of ALE-ITS URGENT

Hi All,
antbody can plz tell me the transaction codes for inbound and outbound process and also plz tell me ALE Message T-Codes.
Thanks,
Maheedhar.T

Under the WEDI and BALE, area menus you will be able to find all the transaction codes pertaining to the ALE.
SALE, WE30, WE31, WE20, WE02, WE21, WE81, WE82, WE41, WE42 etc are the transactins that will help you in configuring ALE.
Regards,
Ravi
Note- Please mark all the helpful answers

Help out for Inbound & Outbound queue

BW Gurus
pl. help me on Inbound & Outbound queue, give details as step by step or any document pl. send it on [email protected]
but i want to understand the through process of it.
assign points if helpful
thanks in advance
charu

http://help.sap.com/saphelp_nw04/helpdata/en/e7/555e3c0f51a830e10000000a114084/content.htm
You can check the tRFCs using tcode SM58 ,and analyze it.
Outbound queue is something which maintains data when it gets posted to R/3. You can check Outbound queue using tcode LBWQ. We generally load the LBWQ data to Delta Queue using JoB Controller.
WE20 is tocode where you maintain Inbound n Outbound parameters. Like which messages to communicate in between Bw & R/3 system.

Schedule lines for outbound process

hi
can anyone tell me what is schedule lines for outbound process
thanks

thanks charlie for your answer can you pl tell me what does it means configured delivery types, item categories and schedule line for outbound processes.
thanks

Troubleshoot: How to process messages in "Recorded for Outbound processing"

Dear Experts,
I have File >XI(3.0)>IDoc scenario with 10-25 interfaces. Per interface an average of 200 msges.
Now we have an issue. from past 6 days all the messages for one of the interfaces are in status: "Recorded for Outbound processing"(with that single small black right arrow) in SXMB_MONI(around 1760 till now). Other than this few 100 messages for couple other interfaces are also in same status. There are other message interfaces using the same Idoc type; but they dont have this problem.
I have checked the queues: SMQ1/Q2. There are no errors. The other threads mention about some reports; but all are for error messages. So that also did not help!
On the first day someone had deleted the error queue entry. They had first checked the message in the queues but that was not showing any status. (This is very strange... but for some messages , the left most status column is not showing any status at all.. but while clicking on the end time column; I am getting the pop up which says succesfully processed). But this is not our problem right now.
Please help me process the messages in the "Recorded for Outbound processing" status.. some how!!!
Thanks in advance for your inputs....
P.N: Runtime workbench here is not configured properly. No CC monitoring tab; message monitoring shows only adapter messages etc.... So cannot check anything here

Thank you for your inputs.
@Udo.... SMQR- no issues.
The RFC destination is fine.
@Abhishek The Idoc has not reached SAP. The xml messages in XI are in "Recorded for outbound processing" which is kinda like Scheduled, i think. Anyway I checked the R/3 cant find the messages or errors.
Any help would be highly appreciated....

OBDLV_PROCOUTP01 (inbound // outbound processing)

Similar Messages

Maybe you are looking for