Output type for movement type for IDOC creation

Dear Experts,
Can anybody tell how to create "Output type for different movement types for IDOC creation"
Specially for Movement type used for Inbound & outbound.

Hi,
pls find below link's
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/abap/idoc%2bsteps
BAPI & IDOC material
IDOC Scenario Steps
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://sap.niraj.tripod.com/id51.html
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
Changing fields in an Idoc segment
Regards
Raj.

Similar Messages

BAPI_GOODSMVT_CREATE for movement type 161, issues in PO creation

Hello Gurus,
I am using movement type 161 with BAPI_GOODSMVT_CREATE in order creating a vendor PO based on the goods receipt posted with the BAPI.
It works fine, nevertheless due to business requirements, I need to apply the following changes:
- in SAP standard the order type is NB by default but in our case I would like to force another order type using the same range that NB. I guess this could be done by activating exit ZXM06U17 (MM06E003). Does someone could confirm it?
- in our process, the purchasing group is not maintained at vendor level (LFM1-EKGRP) but as this field is mandatory in the PO creation and as this data can not be maintained in BAPI_GOODSMVT_CREATE, does someone know if it would be possible to force this value during the PO creation (EKKO-EKGRP) based on a maintenance table? If yes in which user-exit? Exit ZM06U43 could be used?
- furthermore, our specific PO type should have a specific account assignement EKPO-KNTTP instead of the default value U, does someone know if it would be possible to force this value during the PO creation (EKKO-EKGRP) based on a maintenance table? If yes in which user-exit? Exit ZM06U43 could be used?
Kind regards
Chris

Hi Priya,
Just want to share with your guys how to fit this error in BAPI_GOODSMVT_CREATE.
For movement type 161 of PO return you have to pass movement type 101 instead of 161
goodsmvt_item-bwart = 101. After that standard function will determine 101 to 161 automatically and
post that material doc.
NOTE:
In my case
It just heppen only the FIRST time that you do movement with PO Return wich is needed to pass
101 in stead of 161 but after that you can pass 161 the system will continue process correctly.
Hope it help.
Sayan.

Account modification key for movement type 643

Hello Experts,
I am reaching out to you today as I am in need of some info on Account assignment for Goods issue process. I looked at transaction OMWN or OMJJ for movement type based settings. I am running a business process ' Intercompany stock transfer order'. Goods issue movement on delivery reads 643(Goods issue for cross company), which is picking 'Account modification key' VAX.
My requirement was how do I force system to pick VAY for 643 without overwriting VAX with VAY in OMWN transaction. Also there are several possibilities listed out for movement 643 alone. Appreciate if you could briefly tell me how system determines other parameters such as 1) Special stock indicator 2)Consumption posting 3) Value string & 4)Counter to determine 'Account modifier' in the customizing table V_156X_KO for Intercompany movement type 643.
Additional info: Trigger is Stock tarnsfer order type NB. Subsequent process is VL10B for Delivery creation using type NLCC and Intercompany invoice(IV) for shipping the goods to ordering company code. Then in the receiving company MIGO or goods receipt with reference to outbound delivery and fianlly MIRO or Invoice verification.
Regards
SG

Valuation Structure
Data on a material is valuated using the following structure:
Valuation area
Valuation class
Valuation category
Valuation type
Material type
Movement type
Valuation Area
Organizational level at which material valuation is carried out. You can define a valuation area as
follows:
Valuation area = company code
All stocks of a particular material in this company code are valuated together.
Valuation area = one plant
The stocks of a particular material in this individual plant are valuated together. Stocks in
other plants are not included in this valuation area.
You define in Customizing the level at which valuation should take place.
Valuation Class
You group together different materials with similar properties into valuation classes so that you
do not have to manage a separate stock account for every material.
The following table contains examples of possible valuation classes:
Valuation class Description
3001 Colors
3002 Paints
3030 Operating supplies
3100 Trading goods
Which valuation class a material can be assigned to depends on the material type. You can
define the following assignments in Customizing:
All materials with the same material type are assigned to just one valuation class.
Different materials with the same material type are assigned to different valuation classes.
Materials with different material types are assigned to a single valuation class.
MM - Material Price Change (MM-IV-MP) SAP AG
Valuation Structure
10 April 2001
A material is assigned to a valuation class in the material master record. The system checks
whether the material type allows the material to be assigned to the valuation class specified.
The system refers to the valuation class of a material to determine which stock account to post to
when a posting is made for this material.
Valuation Category
Criterion according to which split valuation is carried out:
Procurement
You can valuate a material differently depending on whether it is manufactured in-house
or procured externally.
Origin
You can valuate a material differently depending on where it comes from (such as home
or abroad).
Status
You can valuate a material differently depending on its status (such as new, used,
repaired).
You define the valuation categories in Customizing. A material is assigned a valuation category
in the material master record.
Valuation Type
The valuation type specifies the individual characteristic of the valuation category, such as
internal or external, in the case of Procurement. Within the valuation category Origin, you can
define the different countries as the valuation types. You define valuation types in Customizing.
You first determine all the valid valuation types for a valuation category.
You define in the material master record which valuation types are allowed for a particular
material. For every material subject to split valuation, you must enter all the valuation types
allowed in the material master record.
Material Type
You assign every material to a material type when you create it. Examples of material types in
the standard system include raw materials, operating supplies and finished products.
The material type controls the properties of a material and which data must be maintained for the
material. The following control features are important for valuation:
Is the material managed by quantity?
Is the material managed by value?
Which price control type may be used for the material?
Which valuation class can the material be assigned to?
The system administrator can create or change material types in Customizing.
Movement Type
For every material movement, there is a movement type in the SAP System. The movement type
controls the properties of the movement, for example, which entries you must make when
SAP AG MM - Material Price Change (MM-IV-MP)
Valuation Structure
April 2001 11
entering a material movement, and which updates are carried out when the movement is posted.
The following control features are important for valuation:
Does the material movement cause the quantity to be updated?
Does the material movement cause the value to be updated?
Does the material movement lead to postings in Accounting?
Is the material movement relevant for LIFO/FIFO valuation?
The system administrator can create or change movement types in Customizing.

Print out for movement types

Hi Friends,
How to configure print out for movement type 561 or for scrap ?
Can you pl tell me step by step where and how to configure?
Appreciate your help.
Thanks,
Venkat

Hi Venkat,
What you want to print. if you only want to print out the transaction done thr movement type 561. If you are not going through any development then follow the under mentioned process :
Go to MB51- Select the material, Plant & storage location- put the movement type 561 & 562- select the ranges of date- execute it. System will give the report. Then for print out go to List tab and select the print. After clicking on the print tab, you have to fill some informations like- Output device- Put Locl then No of copies-then click on continue. System will give you to select the printer. Just select and print.
If this is enough then ok otherwise inform me.
Hope this will clear your issue.
T & R,
Brijesh

Reg: i want to get nagative values for movement type 102

Hi All
I have developed a report
in that report
output fields are
po no     mater docment no movement type   qty     netprice
500023     4990                         101              10       100
500024     4556                         102               12       200
this is the output i am getting.
for movement type 102 i want to get the nagtive values .
example
po no     mater docment no movement type   qty     netprice
500023     4990                         101              10       100
500024     4556                         102              -12     - 200
pls can u help
who to write logic
thanks
mars

hi,
use this.
loop at itab.
if itab-bwart = '102'.
itab-menge = - ( itab-menge ).
itab-netpr = - ( itab-netpr )
endif.
endloop.

Transfer Requirement for Movement Type 262 (Cancel With Ref to Reservation)

Hi Experts,
it is possible to configure the system to create a Transfer requirement for movement type 262 (Cancel With Reference to reservation) ?
When i execute a movement type 262 (Cancel with reference to Order), the system creates a Transfer Requirement, i can process it in transaction LB12. Now i am using the movement type 262 to Reservation, but the system does not create a transfer Requirement.
I am using SAP ECC 6.0.
Thanks in advance,
Alejandro López.

Hi Alejandro,
Can you clarify what process you are performing by this comment? .. "_Now i am using the movement type 262 to Reservation"_.
As per standard process TR (transfer requirement) creation takes place as per the setting in IM-WM interface. Please check in Tcode OMLR, if TR create field is having "X" for the warehouse and reference movement type record. Normally whenever any material document gets posted in IM, MM-WM interface provide the decisions about which WM movement type to pick for warehouse and data about TR , PCN and TO creation.
Hope this will help.
Regards,
Sudhir

Transfer Requirement for Movement Type 262 to Reservation

Hi Experts,
it is possible to configure the system to create a Transfer requirement for movement type 262 to reservation?
When i execute a movement type 262 to Order, the system creates a Transfer Requirement, i can process it in transaction LB12. Now i am using the movement type 262 to Reservation, but the system does not create a transfer Requirement.
I am using SAP ECC 6.0.
Thanks in advance,
Alejandro López.
Edited by: Alejandro López on Feb 28, 2011 1:55 PM

Hi Alejandro,
Can you clarify what process you are performing by this comment? .. "_Now i am using the movement type 262 to Reservation"_.
As per standard process TR (transfer requirement) creation takes place as per the setting in IM-WM interface. Please check in Tcode OMLR, if TR create field is having "X" for the warehouse and reference movement type record. Normally whenever any material document gets posted in IM, MM-WM interface provide the decisions about which WM movement type to pick for warehouse and data about TR , PCN and TO creation.
Hope this will help.
Regards,
Sudhir

Is it possible auto TO for movement type 561? if so, how ?

Hello,
Could any one suggest whether auto TO possible or not for movement type 561?
regards
rk

Hello,
when a transfer requirement or a posting change notice is created from the movement type,the transfer orders are created by batch input using the report RLAUTA10 (for transfer requirements) or RLAUTA11 (for posting change notices).
You post the document using 561 movement type. If related setting for auto TR creation (T-code OMKX) is done then TR will be created in the background. You can create the TO automatically from this TR using report RLAUTA10. Refer T-code OMKZ for Auto creation setting. You can also proceed for immidiate creation of TO.
Thanks
Milind

Inspection Lot generation for Movement type 101-O

Hi
I would like to know, which config / Master data need to generate Inspection Lot for Movement type 101-O.
I enter subcontract vendor number and set 'SC Vendor' indicator in purchase order delivery address tab and I created QM data in Material Master.(Insp.Type 01)
While doing GR with reference to purchase Order, stock is Posted to Material provided to vendor - Quality inspection stock. But Inspection Lot
is not generated.
Pl suggest me, What should i do to generate Inspection Lot.
Thanks in Advance.
RRS

hi
Soln 1) Just check whether Inspection is active for 101 - O in SPRO settings if not, activate the same.
Path: Inspection Lot creation/Inspection for Goods Movement
Soln 2) As you flag "SC Vendor" in PO and make GR all stocks will be shown against the Vendor.
From your question I assume that you would like to do inspection for materials coming from Subcontactor end to your Plant:
If this is the case you dont flag "SC Vendor" in PO, make a normal Goods Receipt for the Subcontracting PO, based on Insp setup in Material Master for 01 Insp type Insp lot will be created.
Regards
DC

Auto TO for movement type 531 - Receipt By Product

Hi All,
I have assigned a sloc to WM to make it WM managed sloc , now after doing a MB1A for an Internal order for movement type 531 , i am getting the Transfer requirement created in background for the material doc , but not the TO. Infact the automatic transfer order creation is activated for the movement type , but the automatic TO is getting created automatically for other existing sloc's .Any idea am i missing any configuration ?
Reg
Benny

Hi,
This topic has been dicussed many times on this forum. Please find information on SAP online help:
Auto TO for TR
http://help.sap.com/erp2005_ehp_04/helpdata/EN/97/91cfd2571211d4b3210050045571f7/frameset.htmA
Auto TR for OD
http://help.sap.com/erp2005_ehp_04/helpdata/EN/c6/f8406c4afa11d182b90000e829fbfe/frameset.htm
Immediate TO
Please check OSS note 566090
Maybe you are looking for immediate TO...
Regards,
Csaba

Field Selection error for movement type and G/L account

I am currently experiencing a field selection error between movement type 601 and G/L account 7140000. The problem field is 'Segment'. This field is set to required for the G/L account, but it is hidden for the movement type 601. This inconsistency causes an error when posting the goods movement. According to business requirement the field must be required for the G/L account, therefore we must make this field optional for the movement type.
However, in configuration the field segment does not appear for the movement type 601. Therefore it can not be changed to optional.
Does anyone know a workaround other than making this field optional for the G/L account because the business requirement is to have this field as required?????
Many Thanks

Hi,
On the Error message detail, system will guide you to the Configuration details for Field settings for Movement type & Account, please get in touch with your FI consultant, to make the Field selection for the account similr to that of your movement type, this is a very common issue.
Regards
Chandra Shekhar

Hide/Suppress Cost center field in MIGO and MB1A for movement types 551&552

Hi All,
Can anybody tell me how to suppress or hide the cost center field in MIGO or MB1A for movement types 551 and 552?
I did below settings and it worked fine for only MB1A and for MIGO still it is showing cost center field.
IMG > Materials Management > Inventory Management and Physical Inventory >Goods Issue/Transfer posting > Define screen layout > select movement type to change the option.
Also I did gothrough the settings for Enjoy transaction (MIGO) there we have only option to make fields either "Required entry" or "Optional entry" and we don't have an option to hide/suppress.
Please advise or help me .
Thanks in advance!
Regards,
Praveen

Hi
The cost center field is a required field in mvt type 551 as you are scrapping materials, some cost center will need to take the cost of this operation.
Anyway, you first need to make the field as optional for example, before you move.
One option is that you create a screen variant in Tcode SHD0 for MB1A, where 551 is setup as constant (with content) , and mark Cost center as invisible and assign this screen variant to a transaction in SE93.
regards
Sidi

Issue with Return Delivery for movement type 262

Hi,
I have got a strange issue, the user is trying to do a MIGO Return Delivery for a material document using movement type 262, this he claims has been doing it for many materials. However when i go to the MKPF table i see the transaction Code field to be MIGO_GI for all the material documents for which he claims to have done return delivery. But under this transaction code we have only 4 options - Display, Issue, Cancel and Remove from storage.
Now when he tries to do the return delivery for movement type 262 he get an error message "Check table T156N: entry RL 262 does not exist" , but this has been very well maintained in the table.
Can you please let me know -
If it is possible to do a return delivery for a movement type 262?
If yes how to address the above error encountered.
Thanks in advance
Sachin

Hi Sachin,
If you think of return delivery to vendor with or w/o PO reference you can use movement types 161, 122, 124 as default settings.
Movement type 261 means withdrawal against production order and its reverse is MVT 262. The latter can be used e.g. via MB1A (or you can make storno of a confirmation by 261).
Are you sure your user is using the correct terminology ('return delivery')? Please check the material documents he/she claims to have booked as return delivery. (in MB51 you can get a list of all material movements of MVT 261 that belong to 'your user' and after that you can open the material document and check through which transaction the booking was made.)
BR
Csaba

Error in MB1C but works perfectly in MIGO for movement type 501.

Hi
I get an error in MB1C but works perfectly in MIGO for movement type 501
here is the error Account 353300 requires an assignment to a CO object.
I know for this if we add the co object in OKB9 it works.
But my question is - how it works in MIGO transaction but throws an error in MB1C
Any idea ? has any one faced this kind of an issue ? Please let me know.
Thanks
Dkmurthy

Hi
Are the entires same in both the transactions? Means did you check 353300 GL was hit when you posted through MIGO?
Check in FS00 - for GL account 353300 - under bank/interest tab - double click on field status variant -> under Additional account assignments - CO object is ticked as mandatory?
Thanks

HUMO-A reason has to be entered for movement type 344

Hi All,
We currently have the system configured to enter a 'reason for movement' for movement type 344 and this field is marked as required in the movement type configuration. We have configures the transactions allowed for the movement type and HUMO is one of them.
When I try to post the same HU using the path 'Edit-> Change HU Posting-> Other Postings->Process-> Transfer posting unrestriced to blocked', it prompts me for a 'Reason for Movt' and allows me to post it to a blocked stock.
However, when we try to post an HU to blocked to stock using the path in HU monitor 'Edit-> Change HU Posting->In Blocked Stock', the system gives an error 'A reason has to be entered for movement type 344'. Please note, it does not even prompt me to enter a reason for the movement.
Is there a configuration node to have the above error corrected? Or is there any SAP note which could help us solve the problem? We are aware of the SAP note 1679167 for transaction VLMOVE but not sure the same would actually correct the issue for HUMO. Any help in this regard is appreciated.

Hello Biswajit,
unfortunately, as far as I can see in source
SAPLHUMO
/ LHUMOF04
FORM
/ TRANSFER_POSTING_HU
during debugging, there is no GUI code to ask user for a reason. So it's a lack of functionality.
I think you can add this by an implicit enhancement around FORM transfer_posting_hu asking user e.g. with function module call POPUP_GET_VALUES_DB_CHECKED.
But transfering the entered reason down to the MM posting seems also not so easy because reason field "GRUND" may not visible in that callstack level.
Hope that helps you along
Best regards,
Matthias

Output type for movement type for IDOC creation

Similar Messages

Maybe you are looking for