Posting Level, Doc Type n Mvmt Type

Hi Gurus,
Many thanks for my earlier querry on TP. I have few more things to ask from you experts.
1. What is purpose of Posting Level and Document Type ? How they are different and where we can
create them ?
2. What is the function of Movement Type ? Where can we create the movement type ?
Best regards and many thanks to you in advance.
os

To Anurag Tambe.
A little hint: when you want to provide some links in help.sap.com, then just click on the little red left arrow that you see in the first, topic description. You'll arrive to the proper topis'c link. Instead of giving the link to the whole module, you'll have the precise link, like here:
http://help.sap.com/saphelp_sem60ep1/helpdata/en/3d/c77b3bf7975a03e10000000a114084/frameset.htm
To OS.
Additions to what Anurag Tambe said.
1). Posting levels allow the BCS' user to have information in the system segregated by its origin:
PL 00 - reported data, RFD (plus some changes entered by means of reclasses without document assigned).
PL 01 - some corection to RFD.
PL 10 - some transformation data (very often it's a transformation from a local legislation to GAAP ot IAS).
PL 20 - eliminations between pairs of companies.
PL 30 - entries related to Consolidation of Investments and elimination of unrealised profits in supply chain operations.
It's very useful. At any moment you may see the original (almost) RFD and all corrections/transformations/eliminations etc.
- Document types determine many features, like the PL, currency of the entry etc. etc. They also allow to assign special items to them. In this case you may overwrite the settings set on the system level and allow the system generating specific for the document entries.
2). Movement types is an additional analytic to the items that helps to recognise different types of data. Like Begining balance, increase, decrease etc. In general, interpretaion of the MoveTypes depends on you. You may introduce different types you need. They are to be created in the workbench.

Similar Messages

KR doc type posted without vendor line item a mandatory item category

Hello Gurus,
We have SPL document splitter activated in our ECC system. We have the business transaction variant 0300 / Z001 assigned to doc type KR. The vendor line is obligatory in the above business transaction variant (BTV). THe splitting rule is also assigned for this BTV.
THe problem is that despite having the vendor as obligatory for this BTV, we are able to post the doc type KR (vendor invoice) without the vendor line item e.g.. doc with doc type KR and debit and credit to expense a/c.
Please share your experience if anyone has come across this issue,
Prakash

Hi,
To make the vendor line mandatory for KR document type, you can write the validation as below:-
Step 1:-
Create a message ID via transaction code SE91 for message class /EACC/MSG/ACC_COMP as you want to display to user.
Step 2:-
Go to transaction GGB0 and create the validation step at complete document level in Financial Accounting as below:-
Pre Requisits:-
BKPF-BLART = 'KR'.
Check:-
Create a exit code using user exit and check that line items have at least one vendor line item.
For this take the help of ABAPer and create a copy of the program RGGBR000 and code your check here and assign to the application area GBLR in view V_T80D via transaction code SM30.
Message:-
Message created in step 1 as error message.
Step 3:-
Please also check that this validation has active status (Status=1) at line complete document level (level 3) for your company code in transaction OB28.
Regards,
Gaurav

Customer Invoices with doc types

Hi All,
I want to look for customer invoices based on document types. For ex., all invoices posted using doc type XX. How and where can I look for this information. Any transaction with this criteria or using tables?
Regards,
Satya

Hi,
Here, you have two options i.e.,
1. You can look at the documents by giving Document Type as selection screen parameter at T.Code: FB03 where you can see all the documents related to that Document Type/s.
2. You can see Customer documents at T.Code: FBL5N where you select the range of customers in the selection screen. System would provide the documents related to the Customers. SAP has provided the option called 'Screen Variant', by using the option you can get the Document Type on the screen.
I hope you would understand the options.
All the best.
Regards
Chandra Ponukumati

Restrict User to post 'RE' doc in Tcodes apart from MIRO

I need to Restrict the use of document type “RE”(Inv.receipt- MIRO) while passing manual accounting entries through T code FB01, F-42, F-47, FBS1, F-04, F-51.
I came across a method where ABAP help was required for Object F_BKPF_BLA but can it be done by FI consultant without ABAPer's help ?
Is there any code which we can use? OBA7 has an option to select Batch Input only which will not allow manual posting for doc type 'RE" but not sure whether that will really work.
Experts...pls guide

Hussein,
FNDOPP log file
9/25/13 10:47:48 AM] [Thread-31] Service thread starting up.
[9/25/13 10:47:48 AM] [EXCEPTION] [OPPServiceThread0] java.sql.SQLException: ORA-24067: exceeded maximum number of subscrib
ers for queue APPLSYS.FND_CP_GSM_OPP_AQ
ORA-06512: at "APPS.FND_CP_OPP_IPC", line 85
ORA-06512: at line 1
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:206)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1034)
at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:191)
at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:950)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1225)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3387)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3488)
at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:3857)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1374)
at oracle.apps.fnd.cp.opp.OPPAQMonitor.initAQ(OPPAQMonitor.java:558)
at oracle.apps.fnd.cp.opp.OPPAQMonitor.init(OPPAQMonitor.java:534)
at oracle.apps.fnd.cp.opp.OPPAQMonitor.initialize(OPPAQMonitor.java:89)
at oracle.apps.fnd.cp.opp.OPPServiceThread.init(OPPServiceThread.java:94)
at oracle.apps.fnd.cp.gsf.BaseServiceThread.run(BaseServiceThread.java:135)
[9/25/13 11:04:11 AM] [EXCEPTION] [OPPAQMON:876235] ORA-04021: timeout occurred while waiting to lock object
[GC 20321K->4065K(63360K), 0.0137050 secs]
Thanks,
Vasanth

Validation for GL 23876 to to post only for KG doc type

hi all
i want to write a validation for a GL 238760 this must only be posted only in KG document type it must not post in other doc type like KR nd KZ
i want to write a validation for this.
in the GGB0 screen which message type shall i select and what steps shall i use for this.
please let me know the validation for this function.
Kind regards

Hi:
Please go to GGB0...Create a validation in financial accounting at line item level by selecting line item and create a step. It will open 3 further drop down for you. Select the 1st one and proceed as follows
Prerequisites:
BKPF-BLART = 'KG' (here you can make it transaction code specific as well)
Check:
BKPF-HKONT = '23876'
(you can give set of GL account by creating it in GS01 and specifying it here)
Message:
Assign an error message to it with category E.
Please check this will work .
Regards

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

Error when select posting level in document type

Hi,
Did anyone have an experience to face the Abab run time error when select "posting level" in document type?
The Error is : GETWA_NOT_ASSIGNED
Short text
Field symbol has not yet been assigned.
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_UC_ITKEY_FACTORY===========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.

If you searched the notes, as Dan proposed (and didn't find anything relevant), and the answer to the Greg's question is positive, then I would suggest regeneration data basis and ConsArea due to data model inconsistency.
If it doesn't not help - open customer message to SAP.
Edited by: Eugene Khusainov on Jan 26, 2010 10:26 AM

How to set posting block in BIlling Doc type configuration

Hi All,
Can anybody tell me, How to set posting block in BIlling Doc type configuration.I need to do this to seperate billing creation from from FI/CO posting in my company.
We right now run have the batch jobs which run VF06 & VFX3.
Appreciate any input or suggestions.
Regards,
Vinay

Hi
If you want to check the Manual posting blocks you can configure them through FI/CO. Once you have configured the blocks with reasons it will automatically block for the payments.
goto SPRO-> Financial accounting->Account receivable & Payable ->Business Transactions-> Out going Payments-> Manual outgoing Payments-> Check payment block reason.
Cheers

Document type with posting level 12 not being carryforward

Hi gurus,
We are now implementing SEM-BCS 6.0 in the BI 7.0 server.
We have a document type u201CMIu201D which properties are:
Posting level: 12
Balance check: 0 error when balance note equal to zero
Application: Other
Posting: Manual posting
Inversion: No automatic inversion
The problem is that when we execute the Balance Carryforward in the subsequent year this is the only document type that is not being carryforward.
Why is this happening?
Thanks for your help.
Best regards.

This is by design
http://help.sap.com/saphelp_erp60_sp/helpdata/en/0c/ab0240536fe369e10000000a155106/content.htm
"Data records for preparatory postings for consolidation group changes are neither translated nor carried forward."
I'll try an example...
Company A is sold from company 1 to company 2 in June (EoP)
For periods 0 - 6:
BCS reports company A's balance sheet under company 1
BCS reports company A's income statement under company 1
starting period 7
BCS reports company A's balance sheet under company 2
BCS reports company A's 0 - 6 income statement under company 1
BCS reports company A's 7 income statement under company 2
this is managed through the posting level 02 12 and 22 document types, as well as PL30 if using CoI.
Assuming the period of first consolidation and period of divestiture were set correctly in the groups for company 1 and company 2, BCS wants to read all 0 - 6 data under group 1 and all 7 + data under group 2. This is obviously incorrect from an accounting standpoint and the PCC postings correct that.
So BCS books a PL02/12/22 in group 1 to zero out the balance sheet. It then books another set of entries in group 2 to write up the entire balance sheet in the new group.
However, once you get to the end of the year and run your BCF, the entire balance sheet is now sitting in period 0. The system is able to report company A's balance sheet under group 2 withou the aid of the PCC documents. Therefore, the system does not roll these documents forward into the new year.
The PCC documents were only required because of the periodic nature of the BCS data storage vs. the LTD nature of the balance sheet for reporting. Once the full LTD balance is available in a single period, as is the case just after a BCF, the PCC documents are no longer required.
Anyway, hope that made some sense. If not, I'd encourange you to create an Excel sheet replicating how BCS stores the data in the cube, perfrom a divestiture, and see why the system is not carrying forward the documents. This is how I came to understand it.
Now, if you're doing something "non-standard" with the PL12, all bets are off
Good luck,
Chris

Why use AB doc type with F-04 Post with Clearing Transaction

I am following a script for the F-04 command and it specifies the doc type as AB in the header? Why would you use AB in this case?

Hi Hari Nair Junior,
It's an accounting document type and this document type is general compared with other document type. But then, u also can use GC document type.
Hope this will solve your issue.
TQ
Regards,
Nazrul

ERS functionality for vendor at PO doc type level

Hi All,
If i select ERS settlement for vendor in vendor master record, for all the POs for that vendor , ERS functionality is checked by default. I dont need this ERS defaulting for POs with specific doc type. Its not practical to uncheck for each items in PO where there are more than 1000 line items. Please provide me a solution?
regards,
NBanu

Hi Banu ,
For specific material it is possible through Inforecord but not for specific document type.
Regards
Ramesh Ch

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

Year end and Doc types

Hi all,
I have a question that just came up due to the year end:
we use three doc types for top level adjustment: L1 - permanent, L2 - reverse next month, L3 - reverse next year.
Every month we make a number of specific L2 entries. In december do we still make them as L2, or as L3 type? We have a K4 setup, but only use period 13 actively - there are no postings to 14,15 or 16.
Since we don't run period initialization on 13 in the monitor, they shouldn't reverse then, but when I initialize the new year with Balance Carryover and Period Initialization - will it pick up L2's from December?
Thanks
Pavel

Mani,
Thanks for your reply. I think my question was a little confusing.
L2's do have the automatic inversion within the Fiscal Year. As it is the period initialization task that reverses them, my question was how L2's will be dealt with in December. Since we don't process periods 13-16, does that mean that L2's become permanent?
Dan's answer is probably the best - test in our environment and then we'll know.
As we are trying to close the books today and submit GAAP results to our parent company, we are taking an easy route out: any additional documents will be posted as L3, and when I load January, I will monitor if Dec L2's got reversed. If not, we'll manually reverse them.
In any case, I will post a solution once we load January!
Pavel

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,

Inserting a node in XML and retaining the doc type

Hi All,
I want to insert one new node in an XML. Using the following code I can do that. But the problem is if the XML has doc type declaration then its giving me problem. After inserting the node the transformer is removing my doc type declaration from the XML. I have to retain the doc type definition (including entity declaration) as it is in the original XML file.
The following is the code that I'm using.
Document vDoc = null;
try {
// Contruct the DOM document
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
DocumentBuilder builder = factory.newDocumentBuilder();
vDoc = builder.newDocument();
Node vFormNode = vDoc.createElement("Form");
vDoc.appendChild(vFormNode);
// Convert into a String the DOM document
TransformerFactory tFactory = TransformerFactory.newInstance();
Transformer transformer = tFactory.newTransformer();
DOMSource source = new DOMSource(vDoc);
StringWriter sw = new StringWriter();
StreamResult result = new StreamResult(sw);
transformer.transform(source, result);
catch (Exception e) {
System.out.println("Error: " + e.getMessage());
}The doc type def. in the original file is some thing like this.
<!DOCTYPE article SYSTEM "someurl/TFJA.dtd"[
<!ENTITY T0001 SYSTEM ".\BTN_A_000112809_O_XML_IMAGES\BTN_A_000112809_O_T0001.gif" NDATA GIF>
<!ENTITY F0001 SYSTEM ".\BTN_A_000112809_O_XML_IMAGES\BTN_A_000112809_O_F0001g.gif" NDATA GIF>
<!ENTITY F0002 SYSTEM ".\BTN_A_000112809_O_XML_IMAGES\BTN_A_000112809_O_F0002g.jpg" NDATA JPEG>
]>I know that I can set up the doc type definition in the new XML using the following properties of the transformer.
transformer.setOutputProperty( OutputKeys.DOCTYPE_SYSTEM,"article" );
transformer.setOutputProperty( OutputKeys.DOCTYPE_PUBLIC,"my DTD def");
I cannot hard code the DTD def. as it can vary from one XML to another. Using doc.getDocType() I can get the doctype of the original XML. But is it is not returning the complete def. including entities declaration. Its giving me "someurl/TFJA.dtd".
Is there any way to retain the complete doc type in the original XML file? I don't have much experience in XML and this issue is eating my head.. Also do I have to modify the DTD to accommodate the new tags added in order to make it a valid XML?
Any help and sample code would be highly appreciated.

Hi,
I also had similar requirement and when searching i came across this post. Later i found the solution for this. Instead of hardcoding the doctype you can get it from Document as follows..Snippet from the code i used..
DocumentType doctype = document.getDoctype();
if(doctype != null) {
               String id = doctype.getSystemId();
               if(id == null || id.length() == 0)
                    return;
               transformer.setOutputProperty(OutputKeys.DOCTYPE_SYSTEM, id);
               id = doctype.getPublicId();
               if(id == null || id.length() == 0)
                    return;
               transformer.setOutputProperty(OutputKeys.DOCTYPE_PUBLIC, id);
Hope this helps.
Regards,
Deepak

Posting Level, Doc Type n Mvmt Type

Similar Messages

Maybe you are looking for