New FI AR Doc Type

Hi
For Reporting purpose we want to create a new document type in FI AR. what are stpes to do.
like if we want to copy doc type "DG" to ZG. plz mention congiuration steps. ( with T-c0des ).
Thanks.
Thomas
Moderator: Please, respect the rules of SDN; don't ask for step-by-step and search before posting

For GL , AP, AR . for we define docuemnt type from OBA7. is it correct.
Yes
For new document . Can i assign existing number range used.
Yes
fo new document . can i assign existing reversal document type.
Yes
is there congiruation required for with reference to . Posting Keys.
No
is there congiration required for Screen varient for document type.
No
is any thing required for integration with GL.
No
Regards,
Gaurav

Similar Messages

Change ivoice doc type during sales process flow.

Hi all!
I have encountered a problem:
AS IS:
1. sales order document type is configured in spro field: <b>Dlv-rel.billing type</b> F2    Invoice
2. after delivery I get invoice of type F2
AS SHOULD BE:
1. I need to have a different invoice type created after delivery on a condition based on customer master data.
Is it possible to program it or change copying requirements so that I would get what I need?
I am not interested in new sales order doc type creation.
Best regards,
Michal

Michal,
Your second requirement is standard,
Coming to your second requirement.. Are you expecting to create the billing document through the Billing due list VF04 and get the doc created with specific billing doc type for a particular customer?
                        If So , I don't think you can achive this. I feel you should come up with a Custom billing program or (Customized VF04) where in you can check the Billing due list for a particular period, or delivery range or customers...and based on the customer you can select the target billing type from the Z tables and do a BDC Code for VF01 by entering the target billing type in the screen. Before this you need do to the necessary copy controls for the bililng types you are going to use
                 This is my opinion. Lets see any one proposes any User-Exit to achive this.. Even though I say its not possible, I will wait for our Genious SDN'ers response.
Regards,
Ajai.

New sales doc. type scenario-Urgent

Hi all,
I have got a scenario:
A customer complaint order type has to be made which will take the reference of a Billing doc. Now, based on that Customer complaint order type, Credti memo request and returns order going to be made.
I have made a customer complaint order type Zcut and maintain Item category as Zcat.
In vov8, i have maintained:
created no. range for the doc. type
Check reference mandatory field with "M"
Billing Block field with "06" sign & approval.
In vov7, i have maintained:
Billing relevance "F'
Pricing "X"
I have also maintained copycontrol measures between Biiling doc. and sales doc. with VTAF and between Sales doc. & Sales doc. with VTAA.
Now, when iam creating this doc. type with reference to the Billing doc. , it is not doing following things:
1.no customer name, quantity, amount is getting copied
2. required del. Date is coming as mandatory
can anyone give solution for it. it is urgent
Thanx in advance,
Sourav

Pls check..for VTAF
=>Header level--between ur billing type which i assume is F2 and complaint SO e.g. ZCUT
three routine
DataT 052 Billing doc.header----use for data transfer from VBAK
DataT 103 Bus Data Hdr Billing---use for copying business data
DataT 003 Bill.header partner-----use for copying business partners
=> At item level u wll see TAN which i assume ur using while issue goods..duoble click on TAN...in new screen
ur "ItemCat Proposa" at target sales doc type ZCUT should have ZCAT ie ur return item category
also check following routine
DataT 153 Item from BillingDoc-----use for VBAP data transfer
DataT 104 Bus Data Item Billng-- --use for business data transfer at item level
DataT 004 Bill.item partner-----use for business partners transfer at item level
Copying requirements    303 "Always an item"
Pos./neg. quantity         Blank
Pricing type                  D
Regards
Jagdish

Configuration for new po doc type

Hi guys,
We are on a roll-out project. We want to use new doc types for Purchase Orders and scheduling agreements for the new plant. What are all the configurations required for printing of these new doc types?
Thanks in advance,
Chintu

Hi chintu,
If you have copied new document type NB, No specific configuration is required , maintain a condition record in MN04 for your document type it will generate print based on settings in MN04, if you give out put to be triggered with own transaction use ME9F for taking print out, if you use immediate o/p in Mn04 , once you save the PO it generates a Print
Settings required to trigger the output/type
Copy Message type NEU and create your OWN , and assign new form to this message type , insert this message type in Message Schema
Below is the path :
SAP Customizing Implementation Guide >Materials Management>Purchasing>Messages>Output Control>Message Types>Define Message Types for Purchase Order : Here you can assign your new form and maintain all the setting like NEU
Message Determination Schemas -->Define Message Schema for Purchase Order
Insert your message type here
In order to trigger the Print at document level automatically you have to maintain Condition records
Hope it will help u
Regards
Hareesha

New Sales Area To a New Doc Type

hello fellows
l'm doing config practise.. does anyone address this error i'm getting when i tried to assign a New Doc Type to a New Sales Area
First, maintain the sales area <0999/ZZ/DD> as a common sales area, and then assign allowed sales document types. This means: Complete the IMG activity Assign sales area to sales document types in the sequence entered
HOW DO U MAINTAIN THIS NEW SALES AREA AS A COMMON SALES AREA?
THANKS
RASH

Hi,
IMG-SD-Sales-Sales Doc's-Sales document header-Assign sales area to sales document types-Execute,
Combine sales organizations--enter ur
sales org-- Ref sales org, & save, F3,
Combine Distribution chaneels- enter ur - (OVAM)
Sales org-DC- Ref DC & save , F3,
Combine divisons- enter ur
Sales org- Div- Ref Div & save , F3.
Assign sales order types permitted for sales areas-OvAZ
Ref SO- Ref DC- Ref Div-- sales doc type,
If you have only one sales area, then ref SO, DC & div will be the same in all combinations.
sure it will solve ur query.
*rewards if it solves

Changing doc. type after creating a doc. type.

Hi Friends,
We are doing our time ageing from the time of creating the document in DMS. We created a document with particular doc. type wrongly, after two days we found that the DMS creation was done with wrong doc. type. In this how to transfer to new correct doc. Type, if we delete this & create a new we canu2019t get any info that it was created two days back.
We made Z report for this time ageing report.
Regards,
Sai Krishna

You cannot change the document type after the document has been created. The only way to do this would be with an enhancement and this would create major issues with the integrity of your system

WRP1 excluding open POs based on doc type

Hi friends,
We are using SAP IS Retail ECC 6.0
In our business, we are having requirement that Open PO quantity of particular document type (eg ZNBA) should be excluded from the WRP1 requirement calculation.
Eg:
For an article 100001, Site A001, following are the details,
Reorder point - 10
Target stock - 20
Current stock - 5
Open PO quantity: (ZPO1 and ZPO2 are PO doc. types)
ZPO1 - 2
ZPO2 - 1
Now WRP gives requirement of article as of 12 quantities.
My requirement is to it should not include ZPO1 open quantity in consideration but should take ZPO2 into consideration.
Hence requirement is to create PO for 14 quantities
How do I achieve this?
We have a control in SAP IS Retail where we can specify, that stock of which storage location should be considered in replenishment requirment calculation.
Do we have a similar control for the PO Doc type? If not, how do I achieve workaround?
Thank you,
regards,
Gaurav

Hi,
Do the Following, Create a new storage location., "ZL01"
Whenever your creating a PO with this "ZPO1" document type assin this Slocation "ZL01", then do the below settings in SPRO..
SPRO->Materials Management->Consumption-based Planning->Planning->Define Storage Location MRP per plant.
(In RP indicatior please give "1"Storage location stock excluded from RP, this will exclude the stk from this location)
Regards
GK.
Edited by: Gnana Kumar on Oct 22, 2010 11:15 AM

Assinment of pricing procedure to doc type

Hi friends,
I am new to MM , how the pricing procedure is assigned to doc type, or how the pp is triggered in PO.
Thanks
madhu

Hi Madhu Sudan,
Pricing Procedure as you know is one and the same as calculation schema.
To administer the PP i.e. Determination of Calculation Schema for PO you will have to go to the transaction SPRO---SAP Reference IMG
Follow the node
Materials Management-Purchasing-Conditions-Define Price Determination Process-Define Calculation Schema.
Once you are there In the calculation schema (pricing procedure), you specify which condition types are to be taken into account in which sequence
Now coming to your query,
1) Assignment a Calculation Schema (PP) to Doc type
-- Remember It is not possible to assign PP to Doc type
2) Trigerring of PP in PO
-- Follow these underwritten simple steps:
i. Define a schema group for vendor under the node> Materials Management-Purchasing-Conditions-Define Price Determination Process-Define Schema group. You will have to assign this same schema group in the relevant vendor master record.
ii. Define a schema group for Purchasing organisation under the node> Materials Management-Purchasing-Conditions-Define Price Determination Process-Define Schema group. & assign it to the relevant Purchasing Organisation in the same step.
iii. Once this is done you have to Determine Calculation Schema for Standard Purchase Order under the node>Materials Management-Purchasing-Conditions-Define Price Determination Process-Define Schema Determination. In this step you assign Calculation Schema to a combination of Schema Group (Purchasing Organisation) & Schema Group (Vendor).
iv. Conclusion: During the time of making a PO; Shema Group of Vendor is picked from the relevant Vendor Master Record, Schema Group of Purchasing Organisation is picked from Customisation (where you assigned it) & A Calculation Schema is triggered for the combination of these two Schema Groups (PP that you defined in step iii)
Hope this explains it, for better understanding please read the IMG activity documentation for each activity.
For any further doubts please reply.
Regards,
Prithviraj

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

Anybody ever created multple PO doc type/number ranges in extended classic?

I have searched this forum, and found plenty of useful threads which would help me determine different document types/number ranges for back-end purchase orders in a classic scenario. (And I have done something similar many years ago on a classic EBP 3.0 implementation)
However, I have a customer who has an SRM 5 extended classic implementation, and who (Based on certain simple criteria) requires a different PO number range to identify certain types of indirect orders. (They also have direct materials procured using doc type ECDP, but that's not relevant to this requirement)
This would obviously have to apply to the local PO in SRM, as well as the backend ECC PO.
It would also need to be derived for orders created automatically via approved shopping carts, as well as those orders that are created via sourcing.
I've copied ECPO via define transaction types IMG step, as well as assigned a new number range.
Just to test, I've also added the second doc type in the BSA attribute for a particular test user - just initially see if it was possible to manually choose when creating a PO in sourcing. However, I could only get ECDP and ECPO.
I have looked at various BADIs to see if I can determine doc type or number range somewhere in the PO creation, but as far as I can see, they either:
- Seem to apply only to the object type (PO, requisition, reservation etc) rather than the transaction type within that object.
- Or look like they are too late in the process to influence the doc type and number range (BBP_DOC_CHANGE_BADI?) ... which doesn't seem to have those doc type or PO number fields available anyway
- Or I doesn't seem to be trigerred at all when turning requirement into Po and ordering via sourcing. (tried break-point & endless loop in implemnetation of BBP_CREATE_BE_PO_NEW, but nothing happened. In any case the PO number was alreadya ssigned)
If anybody has ever managed this before, or can tell me that I am definitely barking up the wrong tree, it would be gratefully appreciated. The document type is actually lesss important than the different number range... and was really just an attempt to trigger a different number. I'm starting to think that this sort of thing may only be possible in a classic implemntation.
What I need ideally, would have been some kind of 'local PO' equivelent of the BADI that enables you to determine transaction type for a bid.
Regards,
Vince
Edited by: Vincent White on Dec 6, 2010 5:13 PM

Hi. Not sure on this, but I can tell you that with extended classic it is BADI BBP_ECS_PO_OUT_BADI that is called for the backend PO instead of the CREATEPO_BACK BADI.
You can have a look in BBP_ECS_PO_OUT_BADI and see if that helps?
Don't think it will influence the PO in SRM at all though.
Have you tried the number range / grouping BADIs? They definitly work for changing the number range for classic POs.
Regards,
Dave.

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

Message output for New Purchase Order Document type

Hi experts,
I am having trouble getting a Print message output for a New Purchasing Document type that I created.
Steps that I followed are:
1.Created a new Document type NS via customizing.
2.Assigned the new Purchasing Document Type NS to Output Type NEU which is linked to our customized form for Purchase order display. I used MN04 /NACE to do this step.
Now the message output gets created for my new document type NS but I am unable to display the message.
Notes:
-There are no release stratergies in place for document type NS
-The NEU format works fine the other document type NB which we use for Standard POs.
Are there any steps I have missed? Please help to resolve the issue.
Arosh.

Goto NACE select application EF Purchase Order then goto condition record NEU select condition record select the last key combination "Purchasing Output Determination: Document Type"
here enter your doc. type execute
maintain the condition record
NS VN(function) 1 3 EN and click on communication and maintain
Or goto NACR here put EF and NEU and select the last combination "Purchasing Output Determination: Document Type"
maintain ..
NS VN(function) 1 3 EN and click on communication and maintain
Hope it helps..

Doc. type/item cat.not picking from Purchase Requisition

Hi,
While making purchase order from link with Purchase Requisition, system provides the error message :-
     Doc. type/item cat. ZSUP/ (requisition) <-> ZSUP/ (purch. order)
     Message no. 06054
     Diagnosis
     Purchase requisitions of document_type ZSUP or item category may not be assigned to purchase orders of document type ZSUP or item category .
     Procedure
     Check your input.
     If the problem cannot be resolved in this way, contact your system administrator.
     The latter can make the necessary settings using the Implementation Guide (IMG)
Kindly provide your suggestion how to make PO without account assignment.
Regards,
Satheesh K

Go to the path OLME-Purchase Order-Define Document Types
Here select the document type ZSUP and press Allowed item categories
Check here the standard item category is allowed or not. If allowed, then select the standard item category and press Link purchase requisition - document type
Then click new entry, Select document type ZSUP and then press enter
You will see the below screen
Then save your entry and try again create PO.

5 doc type and 2 content repository

Hi
I have 5 document type in DMS and 2 content repository.
Doc type QWE, ASD, JKL - pdf files must be in content repository X
Doc type ABC, BNM - pdf files must be in content repository Y
How should I proceed to do this?
Regards

Hi,
if I understood your latest information correctly your request is that the files are stored automatically to storage category if you add a file to a document info record and save it. To achieve this behavior the first important setting here are the flags "Checkin" and "Checkin required" which are already set for the used
document status.
This first setting enables the automatic start of the checkin process. But to have a specific storage category choosen for an original workstation application, you have to do another setting and create a profile in your system in the customizing under
- Cross Application Components
    - Document Management System
        - General Data
            - Define profile
For this profile pleasee add your workstation applications under "Determine definitions for applications". Here you can maintain the default storage category for this application in field 'Storage cat.'. Since this profile is created assign it to all your users directly. Then if an user adds a new original file and chooses a workstation application the system should take the storage category automatically from the profile.
Another proposal would be to use the BADI DOCUMENT_STORAGE01 which should offer also methods to control which storage category should be taken for which workstation application. I hope that this information could be useful for you. To set up this scenario in detail I would recommend you to contact your local consulting organization too which will help you in realizing a solution that meets all your requirements.
Best regards,
Christoph

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

New FI AR Doc Type

Similar Messages

Maybe you are looking for