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

Similar Messages

  • Legal Error: Partner Function Mapping not Maintained

    Hello SD Gurus,
    When i create a order and save, i get this pop-up (but i can save the order if i click ok)...
    the pop-up is:
    <u>Legal Error: Partner Function Mapping not Maintained</u>
    Can someone explain why is this appearing and how to correct this?
    Thanks in advance,
    Regards
    Jag

    Hi
    Go to transaction VOPA and maintain partner determination
    In the customer master , VD01 maintain partners for this customer for whom you are creating the sales order
    Hope this helps
    Cheers
    N Ganesh

  • 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

  • ME013 Document type RD33 not allowed with doc. ca tegory B

    When I try to post an SC, i get the following error: ME013 Document type RD33 not allowed with doc. ca tegory B.  I am on SRM 5.0.  I have maintained config (V_BBP_TARGET_OBJ) to create a PO if info complete and I have set up BSA in the org structure as ECPO.  My SC has a source assigned and looks to be complete, yet the system seems to want to create a PR and it is having difficulty doing so.  Any idea on how to troubleshoot this error message?

    Hello Richard,
    I guess RD33 is a PO doc type in your R/3 system.
    In that case, that means your SC tries to create a PR, but with the PO doc type RD33.
    But you said that you defined BSA = ECPO. So where comes RD33 from ?
    Can you tell me what is RD33 in your R/3: PR or PO doc type ?
    And if you have any reference to RD33 in SRM ?
    Rgds
    Christophe

  • The document type does not match any of the given schemas

    Hi,
    I have created an envelope schema.To precisely process inbound envelope documents,in the xml disassembler component i have used the Documentspec and envelopespec properties.
    in the properties i have the the schema name,Assemblyname
    but i have got the error like The document type does not match any of the given schemas.
    I have verified the schemas have deployed properly.
    can you help me on this?

    Hi Sujith,
    As pointed out by Johns lot's of thing can cause this. You have to analyze lot of things, but this kind of error indicates that the message type that you are debatching is not deployed. For Example :
    If you are debatching on Order than Order schema should be deployed in the admin console.
    One more point that you need not to specifiy Documentspec and envelopespec properties until and unless there are multiple schema's of same message type deployed in different assembly. The dissasembler component will automaticaly disassemble the messages
    just looking after the body XPATH.
    Regards,
    Rahul Madaan

  • In ME51N screen service requisition document type is not comming

    Hi gurus,
    Can anybody help me out ,In production server in me51n ie purchase requisition screen, where we used to select the different purchase requisition order types ,service order is not comming whereas in development server it is comming.In spro i have seen the settings ,in document type service order  item category is attached.
    Please help me its urgent.
    Thanks N Regards,
    Siddhartha Chatterjee

    if that document type is not even coming in the spro settings for the production server then i belive it has not been trasported to the production server and that means there has been some intentions to do that so its beeter to make sure that do u really need that document type or not if u need it then try to transport it from qc

  • Document Type is not internet Enabled in DMS BSP?

    Hi all,
    When i test the cvaw_document_change bsp...i hv given a document number and doc type and version...when i click on change....it says "Document Type is not internet Enabled"
    What exact settings needs to made?
    Pl suggest me.
    Rgds
    Pradeep

    For this, you need to "Setup Web Documents".  Define the doc type , here is how to do this.
    Transaction SPRO
    -> Cross Appliction Components
    -> Document Management
    -> Setup Web Documents (BSP)

  • F104 (ERROR: Document type SA not defined)

    Hello,
    Error posting Provisions for doubtful receivales via F104.
    The document type SA not defined!
    I need to create document type SA, or i can use a existing one?
    If i need to create SA, can i create it from a document tyoe model?
    Best regards,
    Bruno Valente.

    you can select SA document for the transaction. or you can create new docment in tcode fbn1

  • How to get change log for fields if change document flag is not maintained?

    Hi experts,
    My requirement is display the change log details for the transaction FAGLGA32.
    In this transaction we have the Field Groups block.if any change is happened for field group we need to capture the change.
    the field for the field group is RKAL1-FGFLG1 and the data element is FGFLG.
    In the data element FGFLG, the flag CHANGE DOCUMENT is not maintained.
    How to get the change log details for the fields for which the change document flag is not maintained at data element level?
    Regards,
    Ramesh

    do a modification for the data element or try Audit Trail (depends on your release)
        Audit Trail (electronic records) / Tx AUT10, AUT01, XX-PROJ-ELR, OSS 564743,517613,564645
            Note 1058984 - FAQ: Audit Trail (Transactions AUT01-AUT10)
            http://help.sap.com/erp2005_ehp_03/helpdata/DE/fc/89683c1b5fb712e10000000a114084/frameset.htm
    cheers
    carsten

  • Period is closed for posting or correct document type is not being used

    Hi All,
    I am trying to post transaction in AB01. But i am getting below error.
    I have checked OB52 and the periods for "+" & "A" are open for 2012.
    Error:
    Period is closed for posting or correct document type is not being used.
    Please assist

    document type i am using is AA.check it other side entery documenttype period open or not

  • Sales document type is not defined for(sales org/division/distribution chan

    Hi Friends,
    I am getting the error that sales document type is not defined for x/y/z(sales organisation/division/distribution channel). while creating sales order.
    Any pointers will be rewarded.
    Regards

    Hi there,
    When you define a sales doc type in VOV8, you also should assign that to the sales area SA (sales org / dist channel / division).
    Only then you will be log a sales order for a sales area.
    Check if you have done it. You will find it in SPRO --> Sales & Distribution --> Sales --> Sales doc header --> Assign sales doc type to SA.
    Regards,
    Sivanand

  • 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

  • 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

  • Error Message : Condition type is not maintained in the schema RM0002

    HI Gurus,
    I have created a new purchasing procedure as follows.
    ZVATV : <b>Condition Schema</b>
    VATV  : <b>Condition Type</b>
    VA : <b>Sch.Grp Vndr</b>
    When I create the Purchase order, the above mentioned schema, ZVATV is automatically determined.
    But when I create Contract, system throws an error message saying condition type VATV is not maintained in the schema RM0002.
    I am very new to SAP, Kindly explain in very detail about this error message and ways to get rid of it.
    If u have got any <b>very detailed material</b> about pricing kindly forward it to my mail id: [email protected]
    Thanks in advance.
    ~Gokul.

    Hi,
    The new condition type you are specifing is the gross price condition (PB00). for PB00 condition type a supplementary pricing procedure is assigned as RM0002. u may have copied the PB00 and changed it to VATV, but with out changing the RM0002. copy the RM0002 and in that also change the PB00 to VATV. after this go to VATV condition type control data (M/06) and assign the new supplementary pricing procedure instead of RM0002.
    The supplementary pricing procedure is required to have the condition types for which no access seqeunce is mentioned. All the condition types in main pricing procedure with out access sequence needs to be mentioned in supplementary pricing procedure.therefore all these condition types will have the same validity periods as PB00.
    Regards,
    Ramakrishna

  • The document type does not match any of the given schemas. batching

    I am aggregating messages(batching) in Orchestation by calling pipeline. I have send pipeline where I have standard assemble component and custom pipeline in encode to assign some values .
    When I test it I get following error There was a failure executing the send pipeline: "Zones._870.Pipeline.Send870Pipeline, Zones.870, Version=1.0.0.0, Culture=neutral, PublicKeyToken=51b3a99d8425ff5a" Source: "ZonesAssignGUID" Send
    Port: "SendToAX870" URI: "C:\File_Out\Ingram\870\%MessageID%.xml" Reason: The document type "http://schemas.microsoft.com/dynamics/2011/01/documents/Message#Envelope" does not match any of the given schemas.  
    Can somebody help me how to resolve this issue? 

    Yes this is configured schema as envelope schema. This one is deployed in biztalk . I tried whatever suggest below query and return one record. Not sure but looks like error message misguiding here.
    select * from BT_DocumentSpec where msgtype like '%http://schemas.microsoft.com/dynamics/2011/01/documents/Message#Envelope%'

Maybe you are looking for