Acct doc type generated in MIGO config

Hi Gurus,
At the time of GR, it is understood, along with one matl document an accounting document would be generated.
How system would know, which type of Acct. doc type need to be picked for Matl document say WE type.
Thanks

Hi,
In SAP all the movement of goods are recorded / symbolise with movement type.When there is movement of goods, A movement type has to be tigered.For ex...........101 Goods Receipt.The move type table has two strings, One is value strings and another is quantity string.The value string updated accounting documents and the quantity string updates the Material document.The value string has transatioin event keys through which all G/L accounts get updated in FI. Exa.........WRX,GR/IR cleraing account.
Regards,
go4s
reward if helpful

Similar Messages

Asset Acct doc and Amt in LC

Hi
When the PO is cread for Asset doc type and the MIGO done.
At the time we were not able to see the Amount in LC tab in GR display doc.
Also at the time thr is no acct doc got generated for the MIGO posting.
Wat could be the pblm.
Vijay

see for the asset accounting all the cost will hit to the asset which u have assigned for itemwise. so please check in the asset accounting it wont show in the amt in lc, hope this will help u.
rgs
santosh

RV Doc Type

Hi,
Our sales order type are YA and YH, YA for cash sales and YH for charge sales. In case of reversal of billing document, doc type generated should be the same as the original document.
There are cases wherein reversal of YH or YA sales generated RV doc type. What could be the reason for this? RV is generated only when we use t.code VF11 for the reversal. We are now using VF02 for the cancellation/reversal of billing document.
How can we prevent RV doc type generation?
Thanks and best regards,
Rachelle

Dear Rachel
Invoice cancellation S1 is a Billing document Type whereas Document type RV is an Accounting document Type.
"Invoice Cancellation type " proposal comes from the Billing document type. You can change the proposal in the Billing document type screen in t.code VOFA, provided the relation must exist in the copy control table.
Whenever a Billing document is saved , always an Accounting document is created in FI ( except Proforma Invoice & if no Posting block).
So there are various accounting documents are available in the standard system & through these document types ,different postings are differentiated.
Normally, from F2 type of Billing document, DR type of accounting document is created.
Similarly, from Billing type G2, accounting document type DG is created.
So, you have to specify these document types in the in the billing type in VOFA, in the "Document type " field.
I mean for billing type F2, specify document type DR & for billing type G2, specify document type DG and so on.
If , you leave this field ( Document type) blank then,
it may be any billing document, System will make the posting in the Accounting document type RV.
That is what happening in your case.So do accordingly.

Prs being generated via mrp need to be in ZI doc type

hi,
we ve just started using MRP to generate prs. these prs are of doc type nb. when i try to use this pr to create sto in me21n.
i get thiss error saying doc type nb cant be converted into U (sto doc type).
earlier we used to create pr in doc type ZI (monthly indent)..using which we were able to create sto as well as local procurement order.
so how do i set PRs generated via MRP to document type zi.
plzz help.
regards
rahul

Hi,
In SAP IIMG the order types of the procurement proposal through MRP run are configured.
Please study the following configuration:
IMG >> MRP >> Procurement Proposals >> Deifne order Profile
Object type     2 Purchase requisition
Order profile   UL
Order type           NB   Standard purchase order
Procurement type     F    External procurement
Special procurement U    Stock transfer
Acct Assignment Cat.
Here I think you need ZI type document.
regards
Datta

Multiple doc type setting for service PR generated from Maintenance order

Hi Gurus,
My client has multiple company code and has different document type for PR and PO as per the company code. For generating the service PR from maintenance order system take the document type of PR defined in the config.
Is it possible to define multiple document type for service PR depend on the company code/ Plant level?
Kindly help.
Regards
DP

Hi Ravi,
I used the User Exit COZF0001 . Since we can assign only one PR doc type in the config .
I have assigned one PR doc type in configuration which will work for a company code and all their respective plant. So in this case user exit wont do any job for changing the doc type.
You will defined a condition in the User exit saying that if company code /plant which you get it from maintenance order is not same (Config ) then provide the PR doc type which you want to create for respect plant or company code.
I dont have coding right now with me. You need a small coding to be done to create the separate PR doc type in EBAN-BSART
with respect to plant . Check in your configuration at what point of time you are creating the PR either in saving or release of MO. You can take the even to activate the User exit.
Consult your ABAPer they can do in 10 min.
DP

Acct assignment to be restricted based on Doc type

Dear All
I need to restrict Account assignments based on Document types,
As of my knowledge there is not standard customizing possible.
But i can restrict Acct assignment based on Item catregory. But this settings doesn't satisfy my requirement,
I would like to know is there any standard customizing or any user exit availble .
Kindly let me know
Thanks & regards
Madhesh Kumar

hi,
there is no sap standard customising for this please go ahead with user exit in PO.
create an doc type.
when you select the perticular doc type system should take default account assignment.
regards

PR generated with different doc type in rollout porject ....why?

Dear Friends.
We have done rollout.
Earlier imlementation - c. code=A200 .
Using standard document type-NB for PR generation.
Latest Rollout - c. code =A100
Using copy of standard document type NB as ZNB for PR generation.
My problem is that when in A100 MRP runs it generates PR with doc. type-NB (NOT ZNB) why?
same way PR generated by Plant maintanace module(PM) in doc.type-NB(Not ZNB) why?
Regards,
Mahesh.

Hi,
Check the below path of configuration, PR created with MRP run have different document type.
SPROMM-Consumption based planningplanningprocurement proposalDefine external procurement.
Hope it will help you
Thanks

Creation of Excise Invoice in J1IS Transaction - using DLFC ref. doc. type

Hi,
I tried to create the excise Invoice using Ref. Doc Type DLFC in J1IS by giving the material document. But it is not allowing me to process further.
The business process requirment is to create a Supplementary Excise Invoice(Customer is Billed for a lesser value earlier)
we tried the following:
1. Credit memo request
2. Credit Memo
3. Excise Invoice in J1IS using sub.Tran Type(to map the Sales exc Inv Accounts). The reson why we used J1IS is to meet the requiremnt of generating the Outgoing Excise Invoice Number which is not possible in J1IH.
Now the issue is, the excise invoice created in J1IS is not available for Utilizaton in J2IUN
Please Suggest what process to be followed to address the issue.
regards,
Girish

In normal circumstances, it is not possible to generate an excise invoice for credit / debit notes in SAP. Moreover, DLFC excise invoice type can be generated only if delivery is involved. So in order to achieve the requirement (and fool the system :-|), you can try by creating a delivery with an item category as TAX so that it will not check for stock, do PGI and invoice (credit memo) can be generated referencing credit memo request. Finally, try to generate an excise invoice via J1IIN
I have never tried this option and hence, its only a guess that this should work. Update after testing.
thanks
G. Lakshmipathi
Edited by: Lakshmipathi on Jul 26, 2011 2:07 PM

Posting of cross company transaction with different doc types

Hi,
The scenario is:-
We have two companies X and Y.
X makes a payment to Y with the following FI entries:-
Company Code X
Dr Vendor Y
Cr Bank HDFC
Company Code Y
Dr Bank ICICI
Cr Customer X
Now this needs to be a cross company transaction where the doc type for CC X should be vendor Payment 'KZ' while the doc type for CC Y should be a customer reciept with doc type 'DZ'.
Although I am able to map the accounts in cross company code config I am not able to split the transaction of different company codes with different document types.
Is there any way we can do this in standard SAP?
Thanks in advance,
Nitish

Hi
As per your issue ...There are no possibilities to post in sap with different document types.
If you want you can post cross company code transactions with one document types
Regards
vamsi

FB05 - trans to be processed and first line item PK for doc type

Hi all,
Me quite confused of the entry for the following document type in FB05
DG - cust credit memo
DR - cust invoice
SA- gl acc doc
SB - gl acc posting
KG - vdr credit memo
DZ - customer payment
Need the help to let me know for document type above, what radio button to choose in transaction to be processed and also what posting key use at first line item.
Also if i choose the wrong transaction to be processed radio button, any impact?
thanks
rgds

Document type is primarily used to distinguish different various types of transactions. Ultimately, there are only two effects in accouting - debit and credit. Thus, doc type helps distinguish btw various types of accounting entries. It also controls certain field status while document posting and also drives the number range for the accounting document.
Posting keys determine whether a transaction will be a credit or a debit. They also have an influence over the field status of the document entry screen. Posting keys are broadly divided into those belonging to
Customer                             - Acct type C
Vendors                               - Acct type V
GL                                       - Acct type G
Fixed Assets                        - Acct type A and
Material Mgmt. transactions   - Acct type M
For each account type there are both debit and credit posting keys. You can clik on F4 on the posting key field and see the various entries. You will understand.
Thus, which posting key to enter depends on the transaction you want to enter.
Regards,

Integration of ECC Scheduling Agreement (Doc Type LP) with SAP TM

Hello Experts,
I am trying to integrate ECC Scheduling Agreement (Doc Type LP) to create OTR in TM System. I have maintained below settings:
1. Create and Activate Control Key
2. Output determination procedure linked to LP has output type TRS0 with requirement 27 assigned.
3. Output condition record has been created
4. I have checked Business Functions are also active
I was able to transfer other Document Types like OR; RE; FD (ECC Free of Charge); SDF (ECC Subsequent Delivery - Free of Charge); Consignment Fill up and Consignment Pick up by maintaining these settings, but not able to push Scheduling Agreement LP to TM.
The output TRS0 is not appearing automatically and if I try to insert and execute this output in Scheduling agreement, Output is failing with error message: "Order is not TM-relevant"
Is there any other config or mapping or SAP Note that needs to be applied to achieve this integration? Because I believe standard integration is available for ECC Scheduling agreement (I have read in help.sap.com).
Thanks and Regards,
Vikram Bhardwaj

Hello Vikram,
You mean this documentation:http://help.sap.com/saphelp_tm81/helpdata/en/9c/787f3c0a771e57e10000000a114084/content.htm?frameset=/en/44/b0488e9c35612be10000000a155369/frameset.htm ?
I think there is talking about the integration for SCM Basis as SOS, not Order Integration.
Regards, Marcelo Lauria

Scheduling agreement with relase - doc type LPA with JIT

Hi
can any one give the steps for Scheduling agreement with relase - doc type LPA with JIT process.. and explain how the JIT will work in SA.
Pls advise what are config required and what the user tcode needed to perform the SA with JIT concept.

Dear Friend,
Without release documentation(Document type LP)
The delivery schedule lines have official character-that is to say,they are transmitted to the vendor as they are saved in the system.The system does not document in detail releases aganist the scheduling agreement that have been sent to the vendor.Therefore,in the case of the document type without release documentation,the message control facility should be set up in such a way that a message is immediately sent to vendor if any changes are made to the delivey schedule stored in the system.
With release documnetation(Document type LPA)
If you use scheduling agreement with release documentation,the delivery schedule lines are not transmitted directly to the vendor.Intially ,the lines of the delivery schedule stored in the system for an LPA scheduling agreement for an internal information only.A message informing the vendor of your material requirements cannot be transmitted to the vendor until you explicitly create an SA release,that is forecast (FRC) or Just in Time(JIT) delivey schedule.Through this process,you can change the way schedule lines are represented.With release documentation,you can disply the SA releases(delivery schedules) transmitted to a vendor over a certain period of any time.This enables you to trace precisely when you sent which information to vendor.
Regards
Pramod

Doc type and drilldown Consolidate data transfered from FI

Dear all members,
I config doc type for data realtime update from FI.
But when i run report CX34, doc type of data transfered from FI to EC-CS is blank.
And I can't drilldown this data.
Please show my mistakes
Many thanks,
Orchid
Edited by: Orchid675 on Jul 2, 2010 5:12 AM

Dear Orchid,
in EC-CS the document number and the document type will be new, the doc type info will not be updated so the original FI doc type will disappear.
Typically, in EC-CS all reported financial data (so documents from FI) will be updated with the same doc type at posting level SPACE (realtime update) or 00 (all other).
I hope my question helps.
Ciao,
David

Fi Document is not generating in MIGO for multiple account assignment in PO

Hi,
I have have created asset po DG set 111 quanity is 4, i have created 4 different assets and assign quanity 1 to each dg sets in account assignment. While doing GRN system is not generating FI document for this po. if i am giving one quanity or single account assignment for as 4 then it is generating FI quantity.
PLease help me out why system is not generating FI document for multiple accont assignment in MIGO.
Thanks in advance
KISHORE

Hi
There is no option if you are not on EhP4... Do MIRO and see if the FI doc is generated
Only way is to do MIRO immediately after MIGO.. OR Schedule ERS (Evaluated Receipt Settlement) which runs every hour in the background so that MIRO is posted automatically based on MIGO document.... Basically, you have to do MIRO after MIGO.. Whether you do it manually or through ERS is a matter of choice
Regards
Ajay M

PR to PO via ME59 -Doc type issue

Hi ,
I am executing the functionality of auto PO and did all the master data settings.
When I convert PR of doc type NB to PO via ME59, then it takes PO doc type as NB.
Similarly, when I convert PR of doc type ZNB to PO via ME59, then it takes PO doc type as ZNB
All of the PO doc types are linked to all PR doc types in configuration. Also nothing is maintained in ' Define default values for document types '.
Please let me know if there is any standard setting wherein PR and PO doc types are linked for auto PO.
Regards

Hi,
If an order document type exists which is identical to the purchase
requisition document type and is allowed according to Customizing (table
T161A or Customizing Transaction OMEC) this one has the highest
priority. If there is only one allowed document type, the system
generates this one. For several allowed document types, the one which is
entered as a default document type for Transaction ME21 is prior to the
others (table T160 or Customizing Transaction OMH5). If nothing is
entered here or the default document type is not allowed, the system
takes the first allowed document type.
The modification solution uses table T160. You can add an entry via
table maintenance (Transaction SM31 or SE16) for Transaction ME59 and
define a default document type (unfortunately not via Customizing
Transaction OMH5) since they are restricted to the transactions, where
the default document type is applied in the standard system. To be able
to use the default value in Transaction ME59, implement the program
change in report RM06BB10 as per note 114213.
Regards,
Mauro

Acct doc type generated in MIGO config

Similar Messages

Maybe you are looking for