Assign Reference Documents

Hi,
Can we assign more than 1 XML result to an XML output property of a transaction? Like, "XMLOutput = Query_1.Results & Query_2.Results".
Regards,
Chanti.

No, but if you use the Union action or merge the two query results inside your TRX and this is eventually what you assign to your XMLOutput transaction property, then assigning the reference document can be made against the merged results.

Similar Messages

Problem with Assign reference document.

Hi all,
I defined transaction input parameter type Xml.
I used Reference Document Loader to load document (structure.xml) below.
<?xml version="1.0" encoding="UTF-8"?>
<SO_VALIDATION>
    <L4_SO_ID/>
    <L4_SOI_NO/>
    <PPC_STATUS/>
    <PPC_INFO/>
</SO_VALIDATION>
I used menu command Assign Reference Document, to assign above document to transaction input.
I tryed to use this transaction in vs.net application as a web service.
But there is no xml structure in InputParams in web service.
I tryed alot but i did not achieve.
What must i do?
Thanks.

cml_bzl,
I'm using version 12.04 and I have not had any problems with assigning reference documents and using .NET.
You should not have to do anyting special to get the transaction inputs to show up in .Net. To map the output I do the following:
1. Create an output transaction variable and assign it's type as XML
2. Using a XML document block to create and XML document for your output transaction variable
3. Assign the XML document as the reference for the output transaction variable.
THis works for me every time. If you change the transaction parameters, make sure you update the web service form the .NET side.
Glenn

Associating a Reference Document to an output parameters

Hello, there!
In my transaction, I create an XML document using the SAP XMII XML Output actions.
Then, I assign this document to an Output parameter for this transaction.
If a put a Tracer after this, Iu2019m able to see my XML perfectly generated.
Now, on my .Net client, Iu2019d like to consume this transaction as a WebService.
But, after the Row elements of the output, nothing corresponds to the real XML that was generated. I can see the output is all messed-up debugging my .Net client.
Iu2019ve found out that this is happening because the WSDL generated by WSDLGen isnu2019t correct. And I can understand why it is so: as the output is generated on-the-fly, WSDLGen cannot know about its structure when constructing the WSDL.
So, is there a way I can associate, say, a Reference Document to my Output parameter, so that WSDLGen can generate the WSDL correctly?
If not, is there another way I can make this thing work?
Thanks a lot in advance!

Your question almost contains the answer...
In the Transaction you will have to assign a reference document (look in the editor's file menu) to the OutputXML transaction property and link it to your IllumDocument (after selecting it don't forget to press the Assign Reference Document button).
If you look in the Link Editor after doing this you will be able to expand your Transaction property and see the document structure - this should then expose it to .NET like you need.
Regards,
Jeremy

Reference documents and account assignment model

Hi gurus,
can anyone explain me the difference in using the account assingment model and reference documents.

Hi,
Account assignment model is defined as a reference for any document entry that provides default values for posting business transactions. This model can contain any number of G/L account items and can be changed or supplemented at any time. yet another point to note is that the GL line items can be incomplete also.
Check out the SAP glossary as below:
http://help.sap.com/saphelp_sm40/helpdata/en/35/2a381e61025cd5e10000009b38f974/content.htm
Whereas in the case of reference documents - data from this type is used to create default entries .
It merely serves as a data source
Thanks
Janani
award points if helpful

Reference Document Functionality - Complaints

Hi
I am working in CRM 4.0
We want the reference document functionality in PCUI when creating complaints.
When we create complaints directly it gives a warning in PCUI "You have not specified a Reference document"
Is there any standard way to go about it.
What we have thought is that we will add a field in header section which will have the R/3 invoice number.(we have done this part)
Throught this R/3 invoice number we have built a function module than can retrieve the product info for this invoice number(this has also bee done)
How do i populate the product info in item level tab in complaints (header level and item level are in different class).
Secondly how do i add the copy button functionality where i can chosse one or more of existing products in the created invoice.
Am i following the correct approach or is their an easier way to go about it.
Regards
Asad

Hi,
You can do it in IMG configuration---MM>Logistics Invoice Verification>Incoming Invoice>Number Assignment>Maintain Number Assignments for Accounting Documents>Document type>Select the document type your using for MIRO>Click on detail>Check Reference number Or you can use t code OBA7.
Hope this helps.
Thanks
Kiran
P.S Pls award points if the answer is helpful.

Format of reference document number is invalid Message no. 8A556

Dear Expert,
I have problem while executing transaction Manual Posting incoming invoice with t-code FB60. The error message shown as written above "Format of reference document number is invalid Message no. 8A556"
I have check the customizing on document type and number range, they are all standard SAP, nothing strange as far my concern.
Could any one give any idea on this problem.
Thanks in advance
Irhasni

Dear Experts,
I have tried to investigate this problem but still have no solution for doc. type KR (Posting vendor invoice)
During investigation on this problem, I did a simulation posting using document type other than KR (assign manually) either by t-cod FB60 or F-02 or F-43, I chose doc. type KA and SA, there is no error when using this doc type, it create Accounting document and Tax line item also appear.
From the simulation I did with this problem, the problem seems on Document type KR (default doc. type for Vendor Invoice). I suspect, it might some setting at other modul likely at MM that control the "Reference" field during document entry... eventhough this field is not set as mandatory at OBA7, it's still saying the same error message.
Is there anyone have any ideas about problem in document type KR?
Thanks in advance
Irhasni

Search Reference document UI not showing up during complaint creation

Hello Gurus,
I am trying to create a Follow Up Complaint from a service request, but when I select my follow up complaint transaction type I am directly navigated to Complaint creation overview page Instead my requirement is I should be navigated to "Search Reference document" UI screen because we wanted to search for ERP Sales Transaction to add items into CRM Complaints.
I know that it can be achieved from Item assignment block of Complaint transaction but I wanted to the ERP Sales order Search option available.
for the same Complaint transaction type when I try to create it by clicking on work center "Complaint", I get the "Search Reference document" UI Screen, I want similar screen when I create the complaint as follow up to CRM Service Request as well.
how do I achieve this?
Thanks
Chandu

Hello Hari,
Sorry for the delayed Response, will check this BADI and if it helps then I will update this thread
Thanks
Chandu

Notification - reference object/reference documents

hi all,
When I create a new notification number for a given notification type in our system, there is a subscreen for reference object (such as material number) and reference document (such as production order number)
Is it possible to have a notification created for more than one material number or more than one production order?
Does this have to be with ABAP defining new screens?
Thanks,
neo

Hi Neo,
there's a new feature since EHP 5.
Check this:
Assigned Objects - Quality Notifications (QM-QN) - SAP Library
This is the only way I know to assign more than one object to a notification (without ABAP),
Chris

Indicating the reference document inside the main document.

Hi,
We have a requirement that indicating the reference document inside the main document. for.e.g: Indicating the sub manuals inside the main manual. Is this possible in SAP DMS. Please suggest me.
Thanks & Regards,
Prasad
Edited by: RPrasad on Jan 4, 2011 5:59 PM

Hi Prasad,
For this you have two options :
1. Use the field Superior document , here you can assign a superior document to sub-document. Configure in DC10 to document
type.
2. Or use Environmrnt -> Document Structure -> Create , here you can create a docuemnt structure means if user is displaying a docuement or using a document for various business activities then user has to refer a document which is assigned in document structure. When someone uses a document if it has a document structure means must refer the assigned document.
Hope this will help.
Regards,
Ravindra

Error in assigning sales document type to sales area

Dear All,
I am trying to assing sales document type to sales area, but system is not allowing me to do that
I am having this error message
" First, maintain the sales area <1000/14/00> 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 here."
Note:
I have never created a distribution channel "14" and division "00" then why system is asking me to define this as a common sales area.
How can I maintain common sales area ?

Dear Ali,
1.You go to VOR1 transaction here you check what is the distribution channel assigned as common distribution channel for your sales organisation and distribution channel ,if it is improper then maintain correct Distribution channel.
2.You go to VOR2 transaction here you check what is the division assigned as common division to your sales organisation and Divisionif ,it is improper then maintain correct Division.
3.You go to OVAO transaction here you assign reference sales organisation to your sales organisations.
4.You go to OVAM transaction here you assign reference distribution channel to your sales organisation and common distribution channel.
5.You go to OVAN transaction here you assign reference division to your sales organisation and common division.
6.Finally you assin sales document type to your referenced sales area.
I hope this will help you,
Regards,
Murali.
Edited by: Murali Mohan.Tallapaneni on Nov 11, 2008 5:58 AM

Reference document of migo transaction

hi,
can anybody tell me how i have to assign reference doument in migo transation?
like we gr against po with mvt. type 101.
now i have made another mvt type 901 by copying101.
my question is how it is decided which mov. type will activate when?
regards
jash

hi
both will be activated and its up to ur use u can use 101 or 901
now u can set ref doc for transaction and not for movement
spro>mm>inve mang>Settings for Enjoy Transactions>Settings for Goods Movements (MIGO)>Settings for Transactions and Reference Documents
her u have to activate the ref doc u need
hope it help
regards
kunal

Number assignment in document types

Hi SDN!
Can I confirm that all number assignment in all document types : Sales, Delivery, Billing , are all meaning the same, that is, number range.
I asked because in billing type, there is a Reference document number at header level. I like to confirm it has nothing to do with this.
regards
Tom

Dear Lakshmi,
I like to clarify my meaning of 'number assignment' .
I mean the document type configuration has this property called 'number assignment'. In sales doc type, it is there. In Billing doc type it is also shown in the books.
So, to conclude, the number assignment referred to in these 2 doc types are different as you explained and sales doc type and delivery doc type number assignment means number range. But that in Billing doc type means reference and allocation numbers.
regards
Tom

Enter manually reference document number in Invoice Header

Hi gurus,
In order to keep a proper numerical sequence of invoices issued in the Company ( between those that are printed in excel and in SAP), we need to set manually a number in the SAP invoice document that we will use to print the form, and that is independent from the one assigned internally.
What would be the best field to set this number?
Reference number (in Header - Accounting data) would be a good choice, but seems like it is managed through copy control and can only be assigned automatically to: Customer PO #, Sales order #, Delivery #, External delivery # and current invoice #. Would it be possible to assigned it manually?
thanks for your always valuable ideas,
VL

Thank you Ken for your answer,
The thing is that we need to transfer this field to accounting, this is why t¡he best choice would be the reference document number.
External range number is not a feasible option because it is required an internal number assignment but the one to be painted in the form and transferred to accounting has to be entered manually in the invoice header.
It is not so easy to enter reference document number manually as it has a copy control assignment as commented in my first note.
Any help would be very appreciated.
Thanks,
VL

Error Plant in reference document and plant do not match

Hi,
I have a problem where in the a shopping created and been approved but the backend communication error shows " 06730 Plant in reference document and plant do not match". The user has used the plant before without having any problem. Please let me know if any root causes.
Thank you,
Manyam

Hello Manyam,
R/3 is raising this message because you are trying to create a PO or PR with a plant that does not match the item reference document.
Reference document can be for example a R/3 contract or a R/3 source list.
It is not possible to change the plant when creating a purchase order with regard to a contract.
Are you using R/3 contract reference in SRM shopping cart ? (maybe coming from catalog item ?)
Did you checked the SOS tab in SRM SC item, to see if the system assigned automatically a SOS (this is the case if only one R/3 SOS is found) ? But in this case, the plant is used as a filter so you could not have SOS from wrong plant.
Rgds
Christophe

Free item reference document number not populated in MIGO item screen

Hi
I have a requirement where in I would need to populate the reference document number in the MIGO item when I am cancelling a goods receipt in case of free items.
In standard SAP system we know that it would only be populated when GRbased IV is ticked in PO but in free item PO this is not ticked . So was enquiring if any body knows how we could populate the reference document number at GR cancellation in MIGO item level for free items .

Hi,
If you mean the field MSEG-SMBLN, then it is always populated at cancellation, no matter the GR-based IV flag.
BR
Raf

Assign Reference Documents

Similar Messages

Maybe you are looking for