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

Similar Messages

PR to PO - ME59 Doc type issue

Hi Experts,
I am executing the functionality of auto PO and did all the master data settings.
When I convert PR of doc type ZNB to PO via ME59, then it takes PO doc type as ZNB.
Similarly, when I convert PR of doc type ZNB1 to PO via ME59, then it takes PO doc type as ZNB1.
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. Your inputs are highly appreciated.
Regards,
Abhijit

Hi Abhijit,
For Automatic PO Creation through ME59 transaction, the PR document type needs to be link to only one PO document type. If the PR document is linked to multiple PO document type then the First PO document type which is available in alphabetical order in table T161A corresponding to PR doc type will be picked and the sytem will try to crete the PO for this document type.
Link the PR document with one PO document and try, issue will get resolve.
Thanks
Shashi
Do give points if the info is useful.

CREDIT MEMO -FI DOC TYPE ISSUE

HI
I have issued credit memo(va01) to customer ..then create billing doc (vf01) against cerdit memo..here automatic account release is there ..system has post the accounting doc .. agaist this invoce .. system alsways take FI doc type RV has taken
generally RV doc type used for std sale order .. i want to assign FI doc tye DG .. to ..credit memo billing doc ..
could any one help in this issue
regards
sesidhar

Hi Sasidhar,
Further to your Query, If the Credit Memo raised from SD Module then the document type would be RV. If same is raised from FI the document type would be DG.
Regards
PG

Sales doc type issue

Hello friends,
while copying the doc typeZOR from standard doc type OR,which fields will not copy ,recently i have faced this question?
Regards,
siva

Dear Siva,
As per my under standing about your question
All data will get copied
But regarding copy control settings system will ask whether copy controls need to be copy or not
If you press yes standard OR copy control settings also will get copy to your ZOR.
If you press no standard OR copy control settings will not get copy to your ZOR.
Settings related to sales document type assign to sales area will not get copy
I hope this will help you,
Regards,
Murali.

Why MKPF-Doc Type showing as Goods Issue, when I did GR via MB1C tx , ?

Hi Experts,
Via MB1C tx, am posting the Goods Receipt (with out PO type) & MBLNR_1 is creating in MKPF.
But, when I saw the Doc type in MKPF for this MBLNR_1, it showing the doc type as Goods Issue type???
pls. clarify me, Why SAP showing it as Goods Issue?
pls. let me clarify scenario? How SAP processing them?
thanq.

Hi Srikhar,
Since the default document type is maintained in the IMG is WA which is for goods issue . it will reflect as goods issue only.
if u dont want this to happen then Go to the tcode OMBA and select good receipt document type ,
Against the toced MB1C,change the documet type as "WE"which is goods receipts.
hope it wud have answered ur question
Reward if useful
Shawn

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

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

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

Conversion Stock Transfer PR into PO via ME59(N)

Hi all,
I want to convert a Stock transfer PR (NB/U) into a UB - PO (UB)
When I do it manually in the ME21N it works fine. But when I use ME59(N) everything points - IMHO - to a Customizing issue -:
errors occur:
"Doc.type/item category (NB/U) (requisition) <-> /U (purchase order)"
"Item Catgory U nit allowed with document type"
I tried "all possible and impossible" settings - can anyone b ring some light to me?
Regards
Tom

Hey,
yes it exists. Was also my first idea. It exists in PR-Customizing for DocType "NB"
This is then linked with the entry
DocType       Description             IC         Dsc. IC
NB     Standard PO              _     Standard     U     Stock transfer
The PO is set up like follows:
NB     Purchase Req Std.          Standard     U     Stock transfer
NB     Purchase Req Std.     U     Stock transfer     U     Stock transfer
Here the "original" error messages:
Doc. type/item cat. NB/U (requisition) <-> /U (purch. order)
Item category U not allowed with document type
So, when the "first part" (NB/U) exists, what could the second "/U" mean??
Any further clue?
Tom

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

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

Delete a line item from Sales Doc type RE

Unable to delete a line item from a sales order linked to document type RE. Get a long runtime - no specific error message. Use the 'Stop Transaction' option to end the transaction.
Have done thorough testing and can delete line items linked to all other sales document types in our system.
Researched SPRO to see if there was a line item deletion option that was not created for sales doc type RE - but can find nothing.
On a critical time line here - this was discovered during Hotpak installation testing which is scheduled to move to PRD June 22. Question as to why we have not run across this issue before now?? - I don't think we have had an occasion to delete a returns line item before - but I want to have the option if available.
Any help to resolve this issue would be appreciated.
Regards
Patsy

Thanks for your response.
After creating document type RE, execute VA02 transaction, select line item, select delete line item icon. The system goes into runtime and just stays there. No error message, no abap dump. To escape the transaction, I have to select 'stop transaction'.
I have tested all other document types we use in our system, (including our customized transactions) SO, CR, DR, etc., and the system allows line item deletion.

Change the backend doc type from PR to PO in BADI BBP_TARGET_OBJECTS.

Hi,
We have followed below approach for backend document type determination.
1. A custom function module contains the logic to determine the backend document type of a Shopping cart line item. THis function module, performs many checks and hence cannot be called in any BADI that is executed in Foreground.
2. I am using BADI BBP_TARGET_OBJECTS to change the follow document type by calling the custom function module.
Issue here is, if the backend document type of a line item is Purchase requisition (2) by SAP standard, and if I try to change it to Purchase order, it gives run time error and ends up in creation of Purchase order.
After further investigation I found that this line item (with default backend doc type as 2) has a desired vendor. If we change the desired vendor of this line item to fixed(To Partner function 19 from partner function 39), it allows us to change the doc type from Purchase requisition to purcahse order in BADI BBP_TARGET_OBJECTS.
But changing the partner function is possible only in BBP_DOC_CHANGE BADI, and I cannot call the custom function module there, as it may impact the performance.
Is there any other way, I can change the partner function in any of the BADIs called in background?
Or Is there any way by which I can change the backend document type from PR to PO in BBP_TARGET_OBJECTS?

Hi Parab
if you swaping 39 to 19 viadoc change badi
REQUESTER has a control on Purchase ORDER Vendor and BUYER lost a control so your business has to decide.In this case procurement department lost their control.
Fixed vendors are like inforecord and contract negotiated for best price ..
Muthu

PO creation: PR or item cat. not assigned to PO of doc type NB

When creating a PO from a PR, client is getting the following error, please help.
The Error is :--
Doc. type/item cat. FO/ (requisition) <-> NB/ (purch. order)
    Message no. 06054
Diagnosis
    Purchase requisitions of document_type FO or item category may not be
    assigned to purchase orders of document type NB 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)
Please let me know what configuration is incorrect or missing.
thanks in advance.

Hi sameer ,
Looking at the error i would suggest to check your IMG settings for the PO document type linkage to PR and allowed Itm Category. IMG > MM> Purchase Order > Document type. In this select the Document type FO and check Item category allowed and Linkage to PR. FO type PO should have been assigned to FO type PR with relevant Itm cat. If not exists assign it.
Hope it answers your query and resolves the issues and don't forget to award the points if it helped you.
Thanks
Kiran

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

PR to PO via ME59 -Doc type issue

Similar Messages

Maybe you are looking for