New created condition types from CRM to R3

I have do initial download with DNL_CUST_CNDALL. The condition customizing(pricing procedure, condition type, condition table...) have been downloaded from R3 to CRM.
In transaction R3AC4(Delta download) two entries for CONDCUSTOMIZING and CONDITIONS exist for delta download of condition customizing and record from R3 to CRM.
But when I created a newe condition type in R3, it is not automatically transfered to CRM. I also tried use transaction R3AR4 (request) to synchronize object DNL_CUST_CNDALL. But the new created condition type is still not availabe in CRM.
Could anyone give some help?
Regards,
Hui Wang

I have restart the DNL_CUST_CNDALL, the new created condition type are transfered to CRM. But when I create another new condition type again in R3, it is not transfered.
Any other advice?
Thanks!
> Hi,
>
> Do the initial load of DNL_CUST_CNDALL once again.
> This should help.
>
> Best regards,
> Vikash.

Similar Messages

New Tax condition type created in ECC, replicated to CRM

Hello All,
I have created a new tax condition type in ECC and through initial load replicate the same to CRM. Even pricing procedure repliction with new tax condition is also successful.
But, the new tax condition is not appearing in condition tab at item level when i create quotation in CRM.
Please advise.
Thanks and Regards
DJ

Hi
Iam facing with the same problem we have created new tax conditon in r/3 and we have replicated it into crm we can find in the pricing procedure of crm as the new tax condition type but iam unable to see that in the order conditions tab.
Could you please let me know the solution or could u please provide me witht he solution. to kmasthanrao at gmail com.
Thanks and Regards
Masthan

Restrict referance of pricing and condition type from latest PO.

Hi Experts,
I am creating Purchase order and at the time of creation of purchase order system is copying prices and condition types from latest PO.
Which is not desirable to our business process, when I dig out I found out that in standard SAP system
The system looks at pricing in the hierarchy order as below:
u2022     Contracts/scheduling agreement
u2022     Condition records
u2022     Info Records
u2022     Last purchase document
So can some one help me with information how to restrict system to follow this referance of pricing.
I want to enter price as well as condition type manualy every time user create a purchasing document.
Also i want to know can it be restricted specificaly for few document type.
Thanks
Best Regards
Ritesh

Hi sir
can we try this
Use the user parameter EVO to indicate that no price adoption from last Purchase Order must take place:
IMG: MM -> Purchasing -> Environment data -> Default values for Buyers
-> Setting for Default values.
Select or setup a default value and on the "price adoption" tab you may choose how copying of conditions from last purchase order must behave. Select "Do not copy".
Then assign this default value to the user, using the EVO parameter.
[http://sap.ittoolbox.com/groups/technical-functional/sap-log-mm/price-to-flow-from-info-record-at-plant-level-813066]
[Re: new info record with same details as archive one.;
check following notes it may helfull
569885 About Info Record Update indicator (EKPO-SPINF)
13127 Update in info record from PO, quotation, contract
430543 FAQ: Purchasing info record
675523
456691
Regards
Kailas ugale

Condition types from Central Contract not copied into Purchase Order

Hi,
When creating a central contract from SRM to ECC, all the condition types are copied well.
But when creating a shopping cart from SRM or a PO in ECC referencing the created central contract, the condtion types are not displayed in the conditions tab. (Only Condtion type PB00 is displayed.).
What can I do to assure, that all the condition types from the contract are displayed in the PO.
Do I have to do some customizing, or is there a SAP Notes to resolve this.
Regards,
Alexander

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

Create Data Type from XSD

Hey guys
i need to create Data Type from and XSD,in the beginning i had an XML document which i converted to XSD using Altova ,then i imported this XSD in IR under External definition,now how should i go ahead with creating Data Type?
my sample XSD is something like this
<?xml version="1.0" encoding="UTF-8"?>
<!W3C Schema generated by XMLSpy v2007 sp2 (http://www.altova.com)>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="WorkOrderNumber">
          <xs:simpleType>
               <xs:restriction base="xs:short">
                    <xs:enumeration value="10942"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="VendorNumber">
          <xs:simpleType>
               <xs:restriction base="xs:int">
                    <xs:enumeration value="109845"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
Its not the complete XSD,just the first few lines.
thanx
Ahmad

Hey Prabhu
my XSD looks like this
<?xml version="1.0" encoding="UTF-8"?>
<!W3C Schema generated by XMLSpy v2007 sp2 (http://www.altova.com)>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="WorkOrderNumber">
          <xs:simpleType>
               <xs:restriction base="xs:short">
                    <xs:enumeration value="10942"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="VendorNumber">
          <xs:simpleType>
               <xs:restriction base="xs:int">
                    <xs:enumeration value="109845"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="UnitPrice">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="MonetaryAmount"/>
                    <xs:element ref="UnitOfMeasureCode"/>
                    <xs:element ref="CurrencyCode"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="UnitOfMeasureCode">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="EA"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="TotalLineItems">
          <xs:simpleType>
               <xs:restriction base="xs:byte">
                    <xs:enumeration value="6"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="TaxTypeCode">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="GoodsAndServicesTax"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="TaxReference">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="GST"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="TaxAmount">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="MonetaryAmount"/>
                    <xs:element ref="CurrencyCode"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="Tax">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="TaxTypeCode"/>
                    <xs:element ref="TaxAmount"/>
                    <xs:element ref="TaxReference"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="Requisition">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="Number"/>
                    <xs:element ref="LineItemNumber"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="Quantity">
          <xs:simpleType>
               <xs:restriction base="xs:decimal">
                    <xs:enumeration value="1.0"/>
                    <xs:enumeration value="2.0"/>
                    <xs:enumeration value="6.0"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="PrimaryCurrency">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="CurrencyCode"/>
                    <xs:element ref="ExchangeRate"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="Pricing">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="UnitPrice"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="PaymentTerms">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="NT30"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="Number">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="Q173849"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="MonetaryAmount">
          <xs:simpleType>
               <xs:restriction base="xs:decimal">
                    <xs:enumeration value="1.98"/>
                    <xs:enumeration value="12.48"/>
                    <xs:enumeration value="12.63"/>
                    <xs:enumeration value="16.75"/>
                    <xs:enumeration value="24.96"/>
                    <xs:enumeration value="240.0"/>
                    <xs:enumeration value="33.84"/>
                    <xs:enumeration value="43.83"/>
                    <xs:enumeration value="5.64"/>
                    <xs:enumeration value="74.81"/>
                    <xs:enumeration value="87.66"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="LineItemTotal">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="MonetaryAmount"/>
                    <xs:element ref="CurrencyCode"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="LineItemNumber">
          <xs:simpleType>
               <xs:restriction base="xs:byte">
                    <xs:enumeration value="10"/>
                    <xs:enumeration value="20"/>
                    <xs:enumeration value="30"/>
                    <xs:enumeration value="40"/>
                    <xs:enumeration value="50"/>
                    <xs:enumeration value="60"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="LineItemMaterialNumber">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="108739"/>
                    <xs:enumeration value="192740-A"/>
                    <xs:enumeration value="380495"/>
                    <xs:enumeration value="43998"/>
                    <xs:enumeration value="54727S"/>
                    <xs:enumeration value="5746"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="LineItemInformation">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="LineItemMaterialNumber"/>
                    <xs:element ref="LineItemDescription"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="LineItemDescription">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="ABSRBT PAD 17 IN X 19 IN X 3/8 IN UNIV P"/>
                    <xs:enumeration value="BSHG HEX 1 IN X 1/2 IN THD FS A105N"/>
                    <xs:enumeration value="GGE 4 IN 1M / 7000 DL SCALE 1/2 IN LM WI"/>
                    <xs:enumeration value="PEN REC RD MED GRAPHIC 39-202"/>
                    <xs:enumeration value="PL ORF 3 IN .5 IN ORF SER 500 316 SS"/>
                    <xs:enumeration value="WPR F-200 FLC NOV LABEL 20"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="Invoices">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="Invoice"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="InvoiceTypeCode">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="ProductOrService"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="InvoiceTotal">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="MonetaryAmount"/>
                    <xs:element ref="CurrencyCode"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="InvoiceSummary">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="TotalLineItems"/>
                    <xs:element ref="InvoiceTotal"/>
                    <xs:element ref="Tax"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="InvoiceQuantity">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="Quantity"/>
                    <xs:element ref="UnitOfMeasureCode"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="InvoiceProperties">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="InvoiceNumber"/>
                    <xs:element ref="InvoiceDate"/>
                    <xs:element ref="VendorNumber"/>
                    <xs:element ref="InvoiceTypeCode"/>
                    <xs:element ref="PrimaryCurrency"/>
                    <xs:element ref="PaymentTerms"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="InvoiceNumber">
          <xs:simpleType>
               <xs:restriction base="xs:int">
                    <xs:enumeration value="98815236"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="InvoiceLineItem">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="WorkOrderNumber"/>
                    <xs:element ref="LineItemNumber"/>
                    <xs:element ref="InvoiceQuantity"/>
                    <xs:element ref="LineItemInformation"/>
                    <xs:element ref="Pricing"/>
                    <xs:element ref="LineItemTotal"/>
                    <xs:element ref="Requisition"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="InvoiceDetails">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="InvoiceLineItem" maxOccurs="unbounded"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="InvoiceDate">
          <xs:simpleType>
               <xs:restriction base="xs:date">
                    <xs:enumeration value="2007-01-25"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="Invoice">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="InvoiceProperties"/>
                    <xs:element ref="InvoiceDetails"/>
                    <xs:element ref="InvoiceSummary"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="ExchangeRate">
          <xs:complexType/>
     </xs:element>
     <xs:element name="CurrencyCode">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="CAD"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
</xs:schema>
can you please tell me how to nest the structures,i m fairly new to XSD and stuffs
thanx
ahmad

Cross-System Copying of Transaction Types from CRM to ECC

Hi Gurus,
We have a requirement where we need to create followup transactions from CRM to ECC.
eg:- We want to create a Sales Order in ECC as a followup transaction to a Service Ticket in the CRM.
1) So please guide what needs to be done inside CRM.
2) Is there some specific list of ECC transactions which could be created as followup to a CRM transaction or any ECC transaction can be created as followup.
thanks for your help in advance.
rgrds,
Randhir

Dear Randhir,
You need to ensure that transaction type and item category of ECC and CRM are in Sync. Maintin followup of your transaction type.
Thanks and regards
Pankaj Kumar

Getting error while creating condition type in SPRO

Hi ,
can somebdy tell me why i am getting the following error while creating condition type in SPRO
No valid change license available for message /sapcnd/
and also while rule determination using condition type we are getting the following error.
system error:system cannot read the structure for table
reg
venkat

Hi Venkat,
Do you have the error number code!?
Regards,
Michel Bohn

Creating IDoc Type from Change Pointers using RBDMIDOC

Hi All,
we are executing program RBDMIDOC(Creating IDoc Type from Change Pointers) evrey 15 minuts in background.
Issue : if some jobs are taking more than 15 minuts then next jobs are failed,
is next job will pick up any idocs that were missed?
there is no extesion's and ther is no Z-fields are used in that message type , we are used OILMAT as mesage type.
Regards,
DSK
Edited by: suresh dameruppula on Aug 5, 2008 2:04 PM

Hi,
Include a step in your job and have a program which checks if a job is already running. If yes do not start the next instance of the same job.
in the custom program just call function module
   CALL FUNCTION 'ZBC_JOB_ALREADY_RUNNING'
      EXPORTING
         JOBNAME           = p_job
      IMPORTING
         JOB_RUNNING       = w_count
      EXCEPTIONS
         JOB_NOT_SPECIFIED = 1
         OTHERS            = 2.
Code within FM ->
   select count(*)
   into   job_running
   from   tbtco
   where jobname = jobname
   and    status = 'R'.
where p_job is the job name.
w_count is current running job count. If its greater than 1, then stop the 2nd with an error message.
Rgds,
Hema

Flowing of the Condition type from Sales Order to invoice

Dear All,
I'm facing a problme in the copying the condition types from Sales order to Invoice.
The details are as mentioed below:
I have a Condition type CONC and made the Copy of the Condition typs as ZDIS.So that CONC's value will be debited and ZDIS' value will be credited in the FI..
But ALL the condition types which i have mentioed including tax and discounts condition types are copying from Sales order to invoice.Except CONC.
I have checked all the copy controls,i'm sure those are OK.Bcoz other condition types are working perfectly fine.
What could be the reason for this???
Will be any setting for on condition type level for copy controls???
Please Guide me its URGENT.
Thanks
Vinay

hi
from which condition type u have copied this CONC , can u pl elaborate more on this.
and just write what is exact scenario and whats going wrong?
in copy controls check for pricing source and pricing type.
regards
mandar

How to create ECC Quotation from CRM Opportunity?

Hi Experts,
Here I am getting an error like "S::000" while creating ECC Quotation from CRM Opportunity. Here I am enclosing the screen shot, please give me the solution.
Regards
Kishor Kumar.

Hi Kishore,
Please check the below links, there are certain per-requisite steps which are needed for this to work.
https://help.sap.com/saphelp_crm60/helpdata/en/47/45839696581a41e10000000a1553f7/frameset.htm
https://help.sap.com/saphelp_crm60/helpdata/en/47/463fc2b61c1a41e10000000a1553f7/frameset.htm
You can also check the SAP Note : 1078575 - ERP sales transactions in SAP CRM for more details.
Hope this helps.
Regards,
Siraj

Creating new pricing condition type in srm ecs

Hi Guru's
I see that there is an option to select the Source system " local" , "other system, eg: R/3" while creating a new condition type in SRM. can you please let me know what is the importance of this? can we determine price in srm using backend pricing conditions? can we invoke the backend pricing procedure from srm and populate the price in SRM PO?
any helpful info would be appreciated
regards
deepu

Hi Nitin,
Appreciate your response. Can you please let me know how major development is it? if you can provide highlights that would be helpful. I do understand that we can customize the pricing procedure in SRM. Can you please share if you have any documentation regarding creating new condition types, access sequences, condition records in SRM similar to ECC? it would be appreciated if you can send it to pradeepwsu(gmail) id.
Thanks in advance
Deepu

Attachment not getting created in PI from CRM

Hi Everyone,
I am trying to create attachments in PI from CRM but it is not getting created there. I am executing the following steps:
By default I am getting the attachment data in Binary format so I am using this function module to convert it into XSTRING format.
          CALL FUNCTION 'SCMS_BINARY_TO_XSTRING'
                          EXPORTING
                     input_length = lv_input_length
                     first_line   = lv_first_line
                     last_line    = lv_last_line
                   IMPORTING
                     buffer       = lv_xbuffer
                   TABLES
                     binary_tab   = file_content_binary.
   2. Then I am getting the server context and the protocol.
                       obj_server_context = cl_proxy_access=>get_server_context( ).
                       obj_attch_protocol ?= obj_server_context->get_protocol( if_wsprotocol=>attachments ).
* Assign File naame to STRING Variable
                       lv_name = lv_filename.
* Attach file to the service response.
                       obj_attachment = obj_attch_protocol->get_attachment_from_binary(
                                  data = lv_xbuffer
                                  type = if_ai_attachment=>c_mimetype_pdf
                                  name = lv_name ).
                       APPEND obj_attachment TO t_prx_attach.
                       obj_attch_protocol->set_attachments( t_prx_attach ).
   3. Then I am using a proxy class which has Input and Output structures for sending data to PI and getting the response respectively. And then in the end I am calling the proxy and passing the structures.
     With this I am unable to see the attachmenmts in sxmb_moni transaction. Please help.

Hi Gurus,
Can you please help with some pointers on this.
I have used below links as reference for coding.
Link 1 :
http://help.sap.com/saphelp_nw04/helpdata/en/a7/3b2a2d45a34a23b75e3b18745c63bc/content.htm
Link 2:
http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/10/19/abap-proxy-protocols-use-cases-and-examples
After setting attachment(Method SET_ATTACHMENTS) i am not getting any exceptions,but still i am not able to see any attachment created in SXMB_MONI.
Thanks in Advance,
Manil.

Prevent new PO message type from being applied when changing an existing PO

I have created a new PO message type for EDI (ZED) which is working as required on new PO instances. Applied conditions are Doc Type, POrg and Vendor, with master data set accordingly.
My problem is when I enter an existing PO in ME22N, which has already been output under an NEU message, the system is applying my new ZED message type and I do not what it to do this.
Also note in Fine Tuned Message Control, I have not set ZED to reprint on changes.
Can anyone help please?
Kind regards,
Neil

This is resolved I didn't need a new message type and deleted ZED. All message outputs now controlled under message type NEU, with required access sequences to suit EDI and other communication types i.e. Print/E-Mail

HOW TO DEFAULT CONDITION TYPES FROM INCO TERMS?

Hi,
I want to Default Condition types based on the Inco terms selected. once the user selects the Inco terms the Corresponding Condition types should default in the Purchase Order.
Ex: For Inco Terms EXW: Ex Works the Condition type Frieght should not Appear whereas For FOB(free on board) frieght Condition should appear.
Is there a Config for this?
How can we do it?
NS

In pricing, please create Price Determination Process based on
incoterms
SPRO -> Materials Management -> Purchasing
-> Conditions -> Define Price Determination Process ->
Maintain Condition Table
create a new condition table (Maintain Condition Table->Create condition table)
for INCOTERM combination and go ahead !

ME21N : Donu2019t copy the price for all condition types from last po

Dear.
When I create a purchase order the price for all condition types are copied from last purchase order inside the info-record.
But I have some condition types like FRA1 or FRA2 that I donu2019t want that system transfer price from last purchase order.
How can I do that ?
Thanks.

Hi Cris,
Go to SPRO>MM>PUR>Info Record>Define Price History> Here with your Purchasing organization if the tick is active that
Specifies that the order price history (PO price history) is to be updated with the effective price.
Normally, the order price history is updated with the net price.
Procedure
Set this indicator if you want the order price history to be updated with the effective price.
Thanks
Diwakar

New created condition types from CRM to R3

Similar Messages

Maybe you are looking for