R3 Document Type mapping in GTS

Hi Experts
Please help how to map newly created document types in ECC with GTS.
T-Code would be great help.
This is required to avoid massage at sales order creation :
SAP GTS: Legal Control: Doc Type Mapping not Maintained (Message no. /SAPSLL/PLUGINR3006)
Regards
AB

Hi Amet,
I am having same issue with our newly upgraded ECC6 box. We get the same message when we try to connect it. Can you please let me know what we need to inorder to fix this.
I guess all PI are incorporated into APPL in ECC6. You reply will be greatly appreciated.
Thanks
-Ramana

Similar Messages

Legal Control : Document Type Mapping not Maintained

Getting an error SAP GTS :Legal Control : Document Type Mapping not Maintained ,while creating order in feeder system .
I checked the configuration maintained SAP Global Trade ServicesSAP Compliance ManagementGeneral SettingsDocument StructureAssignment of Document Types from Feeder Systems-Assign Document Type at Feeder System Group Level
Similarly I checked for item category.
Please let me know what further configuration have to be maintained for correcting the error.
Thanks & Regards

Hi,
The document type mapping is required in R/3 system too. You have to maiatain order type say OR/TA in R/3 below path
IMG--> Sales and Distribution --> Foreign Trade/Customs --> SAP Global Trade Services - Plug-In --> Control Data for Transfer to SAP Global Trade Services --> Configure Control Settings for Document Transfer --> SDOA.
Note: If you maintain OR in R/3, you will have to maintain same in GTS. if you maintain TA in R/3, same maintain in GTS.
Regards,
Lakshmikanth

Output map: Document Type does not match any of the given schemas

On a send port, we have a map that uses a custom xslt. We were hoping to somehow design the map so the output was essentially a generic xs:any schema. But unless we ad a reference from our map assembly to the assembly that holds the actual schema for
the message pertaining to the map out put we get an error:
The Messaging Engine failed while executing the outbound map for the message going to the destination URL "C:\BizTalk\Test\%MessageID%.xml"
with the Message Type http://test#testmessage. Details:"Document type "outputtest#outputtestmessage" does not match any of the given schemas.
Is there a way to avoid having to have the reference?

Hi ,
In BizTalk messages are distinct from each other based on the message type . In your case http://test#testmessage (Namespace#RootNode)
Now coming to your case have you verified whether you have a schema type matching the response is deployed with the solution. The easy way is to look into specific BizTalk application schema node .
If not ,What you can do is to create a new schema for output having "TestMessage" as record and any element inside it. After that apply a mass copy
funtiod from source t destination(in your case any type schema created).
Thanks
Abhishek

Mapping of invoice document type in SRM and Backend

hi,
I need to map invoice document type in SRM and backend. We are in SRM5.0.
e.g. when we create no PO invoice , we need to select document type from drop down and that document type should be replicated to backend invoice document type.
1. There is no list in drop down of invoice document type ( RE/RN)
2. How it will be replicated to back end document type when enter document type instead of selection?
If anyone came across this, pls let me know.
regards,
Rahul Mandale

Dear Poster,
As no response has been provided to the thread in some time I must assume the issue is resolved, if the question is still valid please create a new thread rephrasing the query and providing as much data as possible to promote response from the community.
Best Regards,
SDN SRM Moderation Team

No document type defined in mapping rule

Hi,
Information on document type is need to be loaded from SAP R/3 to BCS for reporting purpose. Customised doc type with assigned role - subassignment already defined. Problem is i still don't see the document type (fiels) for selection in mapping rule (under load from data stream).
Any input would be appreciated. Thanks.
Regards, Renee

Due to reporting requirement, there are certain GLs need to be filter futher by doc type. As long as the document type is successfully extracted from SAP R/3 to BW BCS and filtering is defined in BE Analyzer, i don't need to display it in the report.
Anyway, customised document type already created and doc type can be extracted from SAP R/3. tq

Customs document type cannot be determined for external document Type F8

Hello Experts
Need help
I am trying to transfer F8 to GTS 10.1 and getting following message in GTS Transfer log for export:
Customs document type cannot be determined for external document Type F8
New implementation
GTS 10.1 running with SP 12
ECC side Plug-In settings are fine. BAdi is Active.(There is no document mapping for F8/CUSDEC as it is not required in 10.1)
GTS side configurations are also fine. Checked several times by 4 sets of eyes!!
(Include general settings configurations, Customs communication configurations:)
(Defining technical medium, conditions/output parameters, defining messages for communication process,
defining determination for activity sequence and control settings for communication process)
Despite this I am not able to trnasfer F8 successfully
Can someone throw some light on this issue please?
Keshav Murthy
[email protected]

Hi Dhilipan
Here we go..
You asked me to check the following
Please check following things
1) Legal regulation is activated. - Yes Activated
2) Process template assigned to the legal regulation - Yes Assigned
3) Activity Sequence determination - Yes done
4) Open the activity sequence in under Control settings for Communication processes and check if there is a document type assigned to it. Table- /SAPSLL/TLEPAF - Yes done.
It is really puzzling.
Thanks
Keshav Murthy

Type-mapping not working correctly, get "Unable to find a javaType for the xmlType" WARNING

I'm manually creating a web-services.xml file, and using the autogen ant task to
generate the codec XML/Java classes. The XML definition is provided by SAP.
The ant build.xml file:
<project name="buildWebservice" default="stubgen">
<target name="stubgen">
<clientgen ear="C:\projects\RMIS\ifrrequests\RMIS.ear"
packageName="com.aa.rmis.webservice.client"
clientJar="C:\projects\RMIS\ifrrequests\rmisws-client.jar"
autotype="False" />
</target>
<target name="all" depends="stubgen"/>
</project>
The problem is seen below in the output from Ant. Note the WARNINIG. The problem
is that the xml type cannot be mapped to the Java type.
C:\projects\RMIS\ifrrequests>ant -buildfile clientbuild.xml
Buildfile: clientbuild.xml
stubgen:
[clientgen] Generating client jar for RMIS.ear ...
[clientgen] WARNINIG: Unable to find a javaType for the xmlType:['urn:sap-com:do
cument:sap:business']:PaymentRequest.Create. Make sure that you have registered
this xml type in the type mapping
[clientgen] Using SOAPElement instead
[clientgen] Compiling 4 source files to C:\DOCUME~1\944377\LOCALS~1\Temp\rmisws-
client.jar-836624340
[clientgen] Building jar: C:\projects\RMIS\ifrrequests\rmisws-client.jar
BUILD SUCCESSFUL
Total time: 17 seconds
The Java source that has the implementation of the service methods is simply:
package com.aa.rmis.webservice;
import com.aa.rmis.ifr.request.*;
public class TestService
public TestService()
public int serviceRequest(PaymentRequestCreate request)
System.out.println("Received serviceRequest message");
return 0;
public void testStringRequest(String request)
The web-service.xml file is attached, which contains the schema for the SAP PaymentRequest.Create
object definition.
Another problem I have, which is probably related, is that the service method
that has a complex data type (non-built in data type) is not being deployed into
the WebLogic server. But the other service method that simply takes a String
parameter is.
The steps I took are:
1. Get XML from SAP Interface Repository (IFR) for PaymentRequest
2. Use ant task autogen to generate the request codec classes
3. Create the web-services.xml file by inserting the schema definition and the
mapping file created by the autogen task, and defining the operations
4. Build web-services.war file that contains all autogen compiled class files,
the web-services.xml file, and the service implementation class
5. Build the ear file that holds the web service files
6. Use the clientgen ant task to generate (included above) to generate the client
jar file that should contain the proxy for both of the service methods
Environment:
* WebLogic 7.02
* JDK 1.3.1_06
* JBuilder 9 Enterprise
* Ant 1.4
Possible causes:
* Namespace not being used correctly
* copied verbatim the mapping xml file generated by autogen into the web-services.xml
file
* xml-schema part of web-services.xml might not be set correctly
* operation definition might not be using the correct namespace
* Classpath used for ant might not be right
* Doubt this is the problem, but I'm out of other ideas
* Set by using the setWLEnv.cmd file provided by WebLogic
* Tried adding the generated classes directory for my project to the classpath,
but did not work
I've been referencing the Programming WebLogic Web Services document throughout
this entire process. I must be missing something.
Can anybody from BEA help me out with this problem?
Thanks in advance.
[web-services.xml]

Hi JD,
I spent a few cycles looking over your web-services.xml file, however I
don't have any suggestions other that one that looks like you have
already tried, at the top, in the <schema...>
targetNamespace="urn:sap-com:document:sap:business"
Making edits to these generated files can be tricky and my only
suggestion is to create a small reproducer to run by our outstanding
support team.
A quick look at our problem database shows one issue (CR095109) related
to a similar problem at deploy time that was fixed with 7.0SP3. Again,
the support folks will be able to help focus in on the issue.
Regards,
Bruce
JD wrote:
>
The first posting contains the wrong web-services.xml file. Please refer to this
one instead.
"JD" <[email protected]> wrote:
I'm manually creating a web-services.xml file, and using the autogen
ant task to
generate the codec XML/Java classes. The XML definition is provided
by SAP.
The ant build.xml file:
<project name="buildWebservice" default="stubgen">
<target name="stubgen">
<clientgen ear="C:\projects\RMIS\ifrrequests\RMIS.ear"
packageName="com.aa.rmis.webservice.client"
clientJar="C:\projects\RMIS\ifrrequests\rmisws-client.jar"
autotype="False" />
</target>
<target name="all" depends="stubgen"/>
</project>
The problem is seen below in the output from Ant. Note the WARNINIG.
The problem
is that the xml type cannot be mapped to the Java type.
C:\projects\RMIS\ifrrequests>ant -buildfile clientbuild.xml
Buildfile: clientbuild.xml
stubgen:
[clientgen] Generating client jar for RMIS.ear ...
[clientgen] WARNINIG: Unable to find a javaType for the xmlType:['urn:sap-com:do
cument:sap:business']:PaymentRequest.Create. Make sure that you have
registered
this xml type in the type mapping
[clientgen] Using SOAPElement instead
[clientgen] Compiling 4 source files to C:\DOCUME~1\944377\LOCALS~1\Temp\rmisws-
client.jar-836624340
[clientgen] Building jar: C:\projects\RMIS\ifrrequests\rmisws-client.jar
BUILD SUCCESSFUL
Total time: 17 seconds
The Java source that has the implementation of the service methods is
simply:
package com.aa.rmis.webservice;
import com.aa.rmis.ifr.request.*;
public class TestService
public TestService()
public int serviceRequest(PaymentRequestCreate request)
System.out.println("Received serviceRequest message");
return 0;
public void testStringRequest(String request)
The web-service.xml file is attached, which contains the schema for the
SAP PaymentRequest.Create
object definition.
Another problem I have, which is probably related, is that the service
method
that has a complex data type (non-built in data type) is not being deployed
into
the WebLogic server. But the other service method that simply takes
a String
parameter is.
The steps I took are:
1. Get XML from SAP Interface Repository (IFR) for PaymentRequest
2. Use ant task autogen to generate the request codec classes
3. Create the web-services.xml file by inserting the schema definition
and the
mapping file created by the autogen task, and defining the operations
4. Build web-services.war file that contains all autogen compiled class
files,
the web-services.xml file, and the service implementation class
5. Build the ear file that holds the web service files
6. Use the clientgen ant task to generate (included above) to generate
the client
jar file that should contain the proxy for both of the service methods
Environment:
* WebLogic 7.02
* JDK 1.3.1_06
* JBuilder 9 Enterprise
* Ant 1.4
Possible causes:
* Namespace not being used correctly
* copied verbatim the mapping xml file generated by autogen into
the web-services.xml
file
* xml-schema part of web-services.xml might not be set correctly
* operation definition might not be using the correct namespace
* Classpath used for ant might not be right
* Doubt this is the problem, but I'm out of other ideas
* Set by using the setWLEnv.cmd file provided by WebLogic
* Tried adding the generated classes directory for my project to
the classpath,
but did not work
I've been referencing the Programming WebLogic Web Services document
throughout
this entire process. I must be missing something.
Can anybody from BEA help me out with this problem?
Thanks in advance.
Name: web-services.xml
web-services.xml Type: ACT Project (text/xml)
Encoding: base64

Creation of new document types for document splitting rules

Hi experts,
We have copied from existing SA document type to new document type.
In standard SAP SA document type - define document splitting rule, we have select "NO INHERITANCE OF ACCOUNT ASSINGNMENT", when posting the GL document SA document type without mapping partner profit center,system is control the derive the partner profit center.
Our requirement is copied from existing SA document type to create a new document type - we have created the new dusiness transaction variant and we have map the "classify document type to document splitting rule " and we have selet the "No inheritance of account assignment" while posting in FB01 GL document with out mapping partner profit center system is not control the " derive partner profit center".
Could you please assist us as soon as possible
Thanks ,
Sreenivas
Edited by: sapfico.srini12 on Jan 16, 2012 4:37 PM

Hi,
In order to create a document type for a purchase requisition use the path
spro-materials management - purchasing--purchase requisitions --define document type
in that screen you select the document type you want to copy to create your document type and perform the action.
if you want to change the screen/field selection for your document type select the field selection key (if you select the document type as NBB the field selection key will be NBB.,and go to the screen and change the field status.
Hope this will be suffient for your requirement.
Regards,
Raghu.

Sales document types during initial load

Hi Gurus,
Landscape - SAP R/3 4.6 c, CRM - 4.0
We are starting the initial load for the Sales documents, item categories etc.
For the same, for the document types in R/3, we have the same document type in CRM.
Question 1- Do I need to configure the partner determination, incompletion log etc for the document type before the initial load or I can do it later once the data is in CRM.
Question 2- Is it mandatory that for all the doc types in R/3, we have the respective document type in CRM? Logically yes, if yes, where can I find the mapping? For example for OR in R/3, there is a TA in CRM.
Request someone to answer this ASAP.
thanks
Yash

Hi Yash,
I think the behavior is just use the same code
of Transaction Type in CRM and Order Type in R/3.
Since partner determiniation using different partner
function codes in CRM and R/3, maintained or not in R/3,
you may still need to maintain it again in CRM.
For document, what you can do just create same document
type (Transaction type) for R/3 and CRM. And depends upon
you sceneario (in CRM there are several scenarios such as
document created in CRM and transfered to R/3 Or download
R/3 document into CRM - no transaction in CRM).
Especially for partner, you may need to setup data
transfer CRM to R/3 or R/3 to CRM in CRM configuration.
And in R/3 you need to define it in tcode PIDE.
Hope this helps.
Cheers,
Gun.

New document type for PR/PO

Hi,
I have arequirement where the PO's and PR's are mapped from APO to R3. The requiremtn is the PO mapped should not trigger release strategy. But our release strategy is defined on Doc type/POrg/Value.
So, we suggested for creation of new document type. This document type will not have release stragegy.
Now, the PO coming form APO will be ampped to STO in R3. What all configuration needs to be maintained?

Hi,
Your understanding to exclude document types from release strategy is correct.
For STO Configuration, go to the following:
If the document type created in for Intra Company then in Doc type config against your doc type put T in the Control Colum, if its inter company then this is not required.
Next go to - Materials Management à Purchasing à Purchase Order à Set Up Stock Transport Order à Define Shipping Data for Plants
Here you assign the Sales Area Data for the Plant.
Next go to Materials Management u2192 Purchasing u2192 Purchase Order u2192 Set Up Stock Transport Order u2192 Assign Delivery Type and Checking Rule
Assign Delivery type NL for Intra Company STO and NLCC for Inter Company STO to your Doc Type.
These are basic settings, to understand the complete process you can refer
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c05e2251-91f0-2c10-4e91-e919468e4687

ABAP Data type to XI data type mapping

Hi,
I am creating a message type in XI corresponding to a ABAP structure. There are couple of data types on the ABAP side (for example: RAW, QUAN, CURR CUKY, UNIT, NUMC etc) which i have no idea on what it should be mapped to on the XI side(xsd:string, xsd:token, xsd:int etc).
Is there is any document on mapping from ABAP data type to XML data type ? if yes please send it across.([email protected])
if no doc available, if some body could let me know what these ABAP data type would map on the XI side it would great.
Best Regards,
Kiran

Hi Kiran,
just some more background information to the data types CURR, CUKY, QUAN, UNIT:
1) Each field of data type CURR must be assigned to a field of data type CUKY (the financial amount must be assigned to a currency) and each field of data type QUAN must be assigned to a field of data type UNIT (each quantity must have a dimension). If you want to know this assignment for your specific ABAP structure, you can find it using transaction SE11 with your ABAP structure and go to the tab Currency/Quantity fields. Here you find the information under Reference table and Ref. field.
2) The default number of decimals for a field of data type CURR is 2, but this can be overwritten by the assigned CUKY field. You can check the actual number of decimals for a specific currency with transaction OY04. Here are all currency list that do not have 2 decimals.
3) The default number of decimals for a field of data type QUAN is 3, but this can be overwritten by the assigned UNIT field. You can check the actual number of decimals for a specific unit with transaction CUNI. Click on Units of measurement (pick the correct dimension first), double click on your unit and you find the info in the field Decimal places.
4) Depending on the data you receive your conversions can get quite tricky. Lets take as an example a field of type CURR. If you find the value 1000 in there, this would convert to 10.00 USD if the assigned CUKY field contains the value USD (US dollar). But the same value ca represent 1000 JPY (Japanese Yen) if the assigned CUKY field contains the value JPY. What i try to say is that the value in the field of type CURR alone does not give you the actual amount, you have to know the value of the CUKY field as well. Similar for QUAN and UNIT.
Regards,
Claus

Document Types for PR created in R/3

WE are implementing SRM classic scenario and in version 4.0.
WE are creating the Purchase requisition in R/3 systems.
Now in R/3 we have 2 document types PR01 for Materials and PR02 for services.
There is a badi BBP_SC_TRansfer_BE with method Group_RQ which can be used to
segregate the document types PR01 for material and PR02 for services.
However how do I maintaion the number ranges as in SRM we have only one field where we can maintain the number ranges in cutomising for
Define Number Ranges per Backend System for Follow-on Documents Here it allows only one Attribute for Purchase Requistion.
How do I maintain the number ranges in R/3 as external number ranges for the 2 document types PR01 and Pr02.
Currently I have maintained RQ for Pr01 as external no ranges in R/3.
Is it that I have to maintain RQ for PR02 also or if separate number range than how do I assgin in SRM.
Can any one thorw light on this.
Regards,
Nimish Sheth

Dear Vadim
In Srm we have faclity of maintaining one no range only
In R/3 I have 2 no ranges for Document type PR01(Materials) and PR02(Services)
Is it that I have to keep a common number range with 2 document type in R/3.
IN SRM                         IN R/3
No range                       NO range
RQ - Internl Numbers PR01      RQ - External (PR01)
                               AB - External for PR02
Now how do I map AB in SRM .
or Keep RQ for PR01 and PR02 in R/3
Can you pls throw light on this.
Regards,
Nimish Sheth

PO document type not transferring to Customs management

Hi,
We have configured PO document type in GTS for Import and it got transfer to Complaince not to customs. I have created CULOIM document type and item category on customs. when i checked on this table /SAPSLL/V_TLEYVS i couldn't find CULOIM document type.. When i try to create a new one it say CULOIM document type already exist...
I do not know why it is saying like that even document type not there in that table and where would i find that.
One more question:
When we assign document type to logical system on Customs we can see GTS document type field... when you press F4 you can see CD Cat - A... Can you tell me what is that and where do you define and assign to custom document type.
regards
rc gopi

You can maintain the table by going into the SPRO and defining the doc tyoe you looking for , Onc eyou maintain there it reflects in in this table as it Configuration table.
If you want to delete , add any entry directly in table then u can do that by getting in debug mode.
Select a entry in table
Double click on it
Do /h to switch on the debugging
Press Enter
You will See different Case for "Code"
Type the filed name Code in in "field Name"
it will display the value 'SHOW' you can change this value as desire like to Delete 'DELE' , to insert new value 'AVNO' and then click on change pencil.
and press F8.
Now you come to the screen where u can do the changes and save it.
Custom Doc Category is taken automatically by SAP as for Export and Import doc type in customs it is always A.
If you cDefine Document Types for Advance Docs for Customs Declaration it is C.
Each category has got it one chateristics , so if we defining correct documnet type we need not to worry for category as it will by default come as set in SAP.
Kind Regards,
Sameer

Document type service

We are trying to create a document type service meaning we want to transmit a document
as is. The webservices documentation states:
"RPC-oriented WebLogic Web service operations use SOAP encoding. Document-oriented
WebLogic Web service operations use literal encoding."
Our service method signature is:
public void processCreditApp(String document)
We change our web-services.xml to include: style="document" in the web-service
element and invocation-style="one-way" in the operation element.
The client generated builds a SOAP message with the body content typed as a string:
<env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Body>
<xsd:string>HelloWorld</xsd:string>
</env:Body>
</env:Envelope>
We had expected the content of the body not to be typed with <xsd:string> tags.
Likewise
the generated web service is expecting this typing.
Have the corect assumptions about "literal encoding"? Have we left out any necessary
steps or settings?
We are using WL 7, service pack 2 with the pathch: CR102544_70sp2_v2.jar.

I am not sure I understand. The SOAP body we receive does not have a type designation:
<SOAP:Body>
<diag:Diagnostic
xmlns:diag="http://www.someName.com/namespace.messaging.diag#"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<diag:DiagnosticMessage>
<diag:RequestMessage>HelloWorld</diag:RequestMessage>
</diag:DiagnosticMessage>
<diag:SourceIdentifier>MySource</diag:SourceIdentifier>
</diag:Diagnostic>
</SOAP:Body>
How can we map types for this?
Steve
"Karthik V" <[email protected]> wrote:
Just by changing "rpc" to "document" in web-services.xml will not help.
You missed <types> and <type-mapping> elements.
I guess your <operation> still has input param type as xsd:string.
You should change this to new type that you create to represent your
document.
Alternatively, you could servicegen with style="document" and take a
look
at the generated web-services.xml.
That will give you a better idea.
/k
"Steve Watson" <[email protected]> wrote in message
news:[email protected]...
We are trying to create a document type service meaning we want totransmit a document
as is. The webservices documentation states:
"RPC-oriented WebLogic Web service operations use SOAP encoding.Document-oriented
WebLogic Web service operations use literal encoding."
Our service method signature is:
public void processCreditApp(String document)
We change our web-services.xml to include: style="document" in theweb-service
element and invocation-style="one-way" in the operation element.
The client generated builds a SOAP message with the body content typedas
a string:
<env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Body>
<xsd:string>HelloWorld</xsd:string>
</env:Body>
</env:Envelope>
We had expected the content of the body not to be typed with <xsd:string>tags.
Likewise
the generated web service is expecting this typing.
Have the corect assumptions about "literal encoding"? Have we leftout
any necessary
steps or settings?
We are using WL 7, service pack 2 with the pathch: CR102544_70sp2_v2.jar.

Multiple document types per Network in Purchase Requisition stage

Hi,
PRs get created automatically whenever we attach the material component to an activity.Required Document type of PRs are maintained in transaction 'OPTT'.
My Client is using three document types for Imports, Material Procurement & Services Procurement respectively & he wants all the three document types to be mapped in Project System implementation.(All other modules have been implemented long back & now IM&PS modules are being implemented)
In transaction OPTT, only one entry is possible to maintain as Document Type. Can anybody share how to maintain three Document Types?
Thanks
Kishore

Hi Kishore
Let me clarify one thing that Tcode:OPTT is to specify purchasing item categories(account assignment categories) and a purchasing document type for purchase requisitions in the network, this is not the area where u create new document type.
1) u can create new document types in the IMG>Material Management >Purchasing > Purchase requisition>define document types. where in u have define the new document type with the allowed categories and link purchase requisition with the document types.
2) U have to link this document type to the PO document type.
3) Then go to the OPTT transaction maintain the account assignment categories for the new document type created.
Reward points if useful
Regards
Murali

R3 Document Type mapping in GTS

Similar Messages

Maybe you are looking for