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
Similar Messages
-
Sending Idocs from Change pointers
Hi All,
When using RHALESMD or RBDMIDOC, is it possible to send Idocs with transfer mode Insert instead of Update?
Currently when I create new P objects and run the programs the Idocs sent is of transfer type Update. But since the object doesn't exist in receiving system there is nothing to update.
Please let me know if you have any thought what action i can take to solve this problem.
Best regards
MikaelDear Karyna,
The data is fetched from tables TBDME and TBDA2. Neither of the tables has partner system.
You can use below parameters by copying the program and modifying as per your requirement. See if you can link them to receiver partner system.
The data is fetched from TBDME.
You can use below parameters.
MESTYP Message Type
REFMESTYP Reference message type
IDOCFBNAME ALE: IDoc editing function module
OBTAB Name of database table for object
CREUSER Created by
CREDATE Created on
CHAUSER Changed by
CHADATE Changed On
OBJTYPE ALE Object Type
REDUCIBLE ID for reducible message type
BDCP2_SUP Message Type Supports Change Pointers in Table BDCP2
Table TBDA2:
MESTYP EDI_MESTYP
ACTIVE ALE_ACTIVE
BDCP2_ACT BDCP2_ACT
Regards,
Naveen. -
ALEREQ idoc type from PI system
Hi,
I have to change the vendor data from Inbound idoc which will be coming from PI system.
but, to get the inbound idoc for vendor we have idoc type as CREMAS05 and message type as CREFET
But,at PI side to send the vendor data, they see the idoc type as ALEREQ01 for message type as CREFET.
Kindly provide me the resolution.
Thanks in Advance.hi
yes u can export an idoc from r/3 to a legacy system.
the brief outline is as follows:
1. set up an rfc connection. it has to be 'T' type in t-code sm59
configure the saprfc.ini file if on windows based os. if on unix based os configure rfcexec.c to have the login details of apo system.
2.set up logical systems( at least 1 each for r/3 and apo) using T-code SALE.
3.assign clients to the logical sytems using T-code SALE..
4.create ports using tcode we20.
5. create idoc segments using we30 and release.
6. create idoc type using we31.
7. create message type using we81.
8. assign message to idoc using we82.
9.build a customer model using tcode bd64.
10. create an outbound process code usint tcode we41.
it will help if you specify your idoc that you want to use- for vendor, customer and material there are predefined distributions and idocs.
Thanks. -
Hi folks,
I've created a new Idoc segment for an existing idoc (The original idoc doesn't have the fields I need). I'm now trying to create a new Idoc type taking into consideration the new Idoc Extension I've created. When I type my new idoc type and select 'basic type', I believe I should get prompted (somewhere) to enter the Basic Idoc type and Extension type, but when I create a new basic type, I don't get the option to add my new extension. And If I copy the original basic type, I don't get my new segments.
Can someone please tell me what I'm missing in the create new Idoc Process?
Cheers,
SteveHi Stephen..
According to ur Scenario (Adding new Segments to a Basic type ) , you should not create a Basic idoc type . Rather you should create an Extended idoc type in WE30.
That will ask for the Basic type and the new segments can be added here.
This is the Complete info:
1.
IDOC Enhancement
This is the Complete Steps and Info on this...with an Example...
Enhancing ALE
For example, if in an outbound interface you find that the IDOC type does not contain all the data you need to pass to the other system, you can extend the IDOC to accommodate the additional fields and enhance the ALE function modules to populate the fields. Similarly, if in an inbound interface, there is additional data that needs to be posted to the R/3 application, you can extend the IDOC type to have additional fields populated by the external system or translator or the other R/3 system and then enhance the inbound ALE function modules to post the additional data to the R/3 application.
let us use the SAP Customer Master application as an example. Specifically, letâs focus on the IDOC extension and ALE function module enhancement of IDOC type DEBMAS02 and message type DEBMAS (Customer Master) and the IDOC reduction of message type MATMAS.
IDOC EXTENSIONS
Letâs first look at the concept of IDOC extension. SAP delivers Basic IDOC types such as DEBMAS02, MATMAS02, ORDERS02, and WMMBID01. By extending the Basic IDOC type, you are actually creating a new IDOC type. You create a new segment with the additional fields. This new segment has to be associated with one of the existing Basic IDOC segments. Then you create a new extension type, which is associated with the Basic IDOC type. This results in a new IDOC type. In order for ALE function modules to relate to this new IDOC type, the IDOC type is linked to the corresponding message type.
Note that you should not add fields to existing segments but should create a new segment and associate it with an existing segment. This, in a nutshell, is the process of creating IDOC extensions.
In our example, the Basic IDOC type DEBMAS02 is used to communicate Customer Master data to the SAP Customer Master application. Even though the application has a screen to enter and store a contact personâs business address (see Figure 1), DEBMAS02 does not have a segment or fields that communicate the contact personâs business address. If your business requires that this business address be communicated to the other system through the ALE interface for Customer Master, then you have to extend the DEBMAS02 IDOC type, and enhance the corresponding ALE function module.
In DEBMAS02 the contact person fields are present in segment E1KNVKM and the business address of the contact person is stored on the SADR SAP table. You need to create a new segment, Z1SADRX, that is associated with E1KNVKM. This will be done in the process of creating an extension type ZDEBMASX. This extension type will then be associated with a new IDOC type, ZDEBMASZ. IDOC type ZDEBMASZ will be linked to message type DEBMAS for Customer Master. The final step in the IDOC extension process is to check the new objects. This check also verifies the structural integrity of the IDOC type. Letâs look at each of these steps in more detail.
1. Create an Extension Type and a New Segment.
Determine the fields on table SADR that you are going to provide for in the new segment Z1SADRX. You need fields for name, street, city, region, and country to give the business address of the contact person. You also need fields for the address number. ADRNR is a field in SAP tables such as SADR that uniquely identifies the address of an entity. This field is cross-referenced from other tables to the SADR table to obtain the full description of the address. Because this is an IDOC type for master data, the first field of the new segment will be MSGFN. The message function field informs the receiving system of the action to be taken for that particular segment. In the code that you write for populating the new segment, the value of the message function is the same as that of the parent segment E1KNVKM. In all, you will have 12 fields in segment Z1SADRX (see Table 1).
To create an extension type and new segment:
Use transaction WE30 or from WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object Name.
Choose Extension Type.
Click on Create.
You will see a pop-up screen. Choose Create New, and enter a description. For version 4.x, enter DEBMAS02 in the Linked Basic Type field. Enter.
You will see a screen with ZDEBMASX and its description in the first line. Click on this line, and press Create. For version 4.x, expand the tree of segments, and place the cursor on E1KNVKM.
You will see a pop-up screen. Enter E1KNVKM as the reference segment. Enter.
For 4.x, press Create after placing the cursor on segment E1KNVKM.
You will see a line appear with E1KNVKM hierarchically below ZDEBMASX, with a description "Customer Master contact person (KNVK)."
Click on this line and press Create. You will receive a message indicating that the new segment being created will be a child segment of E1KNVKM. Enter. A pop-up box appears for the new segment.
Enter Z1SADRX as the segment type, 1 for Minimum, 1 for Maximum. Leave Mandatory segment unchecked. These entries imply that there is only one Z1SADRX segment for every occurrence of the E1KNVKM segment, and also that this segment is not mandatory. Note that if the parent segment is not mandatory, then the child segment should not be mandatory, because this could result in a syntax error during the creation or processing of the IDOC.
For 4.x, you must first create the IDOC segment Z1SADRX (Iâll explain why in a moment) from the menu path WEDI -> IDOC -> Development -> IDOC Segment.
Click on Segment Editor.
On the next screen, click on Create.
Enter a development class for the object. Enter.
This will take you to the screen for segment definition. Enter a description for the segment. Enter the field name, data element, and the data element documentation name. In most cases, all three fields may have the same values. If you are using a field in the segment that is not present in the ABAP/4 data dictionary, you must first create the domain, data element, field, and appropriate documentation before using it in the new segment.
Enter these three columns for all 12 fields. Save.
Click on Generate/Activate, F3 to step back.
From screen Maintain Segment, go to Segment Type -> Release. A checkbox now appears beside the segment definition Z1SADRX (see Figure 2). Check this box. Save.
Save again to store the descriptions of the segment, F3 to step back.
Save the extension type.
It is possible to have several new segments with relevant Basic IDOC type parent segments in a single extension type. However, you can form only one IDOC type based on a single extension type.
2. Create an IDOC Type.
The next step is to create an IDOC type by associating the extension type that you created with the Basic IDOC type. This is a simple process:
From transaction WE30 or WEDI go to Development -> IDOC Types.
Enter ZDEBMASZ for Object Name.
Click on IDOC Type.
Click on Create.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter a description.
Enter.
You will see a display of the composite IDOC type with all segments, including Z1SADRX (see Figure 3).
It is possible to associate only one extension type with a Basic IDOC type for a given IDOC type. However, you can have multiple new segments in an extension type.
3. Link IDOC Type to Message Type.
The next step is to link the new IDOC type to its corresponding message type. This is important, because this relationship is referenced in the partner profile parameters where you specify the message type and IDOC type to be used for that particular representative system. To link the message type:
Use transaction WE82, or from WE30, go to Environment -> IDOC Type / Message Type, or from WEDI go to Development -> IDOC Type -> Environment Î IDOC Type / Message Type.
Click on Display <-> Change.
Click on New Entries.
Enter DEBMAS for message type.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter your SAP R/3 release number for Release.
Save.
This data is stored on the EDIMSG table and is accessed by several ALE processes to relate the message type to the IDOC type.
4. Check the IDOC Type.
Before checking the IDOC type for consistency, it is important to perform another step that releases the extension type to the IDOC type:
From WEDI go to Development -> IDOC Types -> Extras -> Release Type, or from transaction WE30 go to Extras -> Release Type.
For the Object Name ZDEBMASX and radio button Extension Type, click Yes.
The extension type has now been "released."
You canât edit the extension type once itâs released. To cancel the release for further editing or deactivation, go to WE30 Î Extras Î Cancel release. The final step in the IDOC extension process is checking the validity of the IDOC type:
From transaction WE30 or WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object name.
Click on Extension Type.
From the Development Object menu select Check.
Repeat the operation for IDOC type ZDEBMASZ.
A check log will be generated for each run with details of correctness or errors (see Figure 4).
In some situations it is possible to receive errors during the check process, especially segment length errors. The incorrect IDOC segment can be repaired and corrected by executing program RSEREPSG. This program checks the formal consistency and repairs incorrect segments. In test mode it will generate a log of formal correctness for the specified segment only. For the program to repair segments in normal mode, the underlying IDOC structures (DDIC structures) must be active. This program rectifies the lengths of the DDIC structures and not the fields themselves. RSEREPSG can also be used to change the person responsible for the object and the release flag.
Menu paths may vary slightly depending on the release/version of SAP R/3, but the procedures and the principles are the same.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
Reward if Helpful. -
Is it Possible to import an IDoc type from R/3 into APO system
Hi Gurus ,
Could you please guide if we can import an IDoc type from R/3 system to APO system ?? If yes , can you please give the guidelines / step - by - step procedure for this.
Thanks in advance ,
Roselinehi
yes u can export an idoc from r/3 to a legacy system.
the brief outline is as follows:
1. set up an rfc connection. it has to be 'T' type in t-code sm59
configure the saprfc.ini file if on windows based os. if on unix based os configure rfcexec.c to have the login details of apo system.
2.set up logical systems( at least 1 each for r/3 and apo) using T-code SALE.
3.assign clients to the logical sytems using T-code SALE..
4.create ports using tcode we20.
5. create idoc segments using we30 and release.
6. create idoc type using we31.
7. create message type using we81.
8. assign message to idoc using we82.
9.build a customer model using tcode bd64.
10. create an outbound process code usint tcode we41.
it will help if you specify your idoc that you want to use- for vendor, customer and material there are predefined distributions and idocs.
Thanks. -
Basic Standard IDOC type v shall b using which is relevant to our scenario
Hello Everybody,
We need to use SAP ALE functionality to transfer the date instantaneously.
The interface is designed to transfer ABC employee's attendance & absence data to XYZ SAP instance for time evaluation and payroll transferring.
Can anybody let me know the general scenario v follow for this interface to happen.
for e.g. :
Start--> Remote system call > IDOC_INBOUND_ASYNCHRONOUS>Pass communication to the system > User ID validations-> Data in Control Records ---> ALE Services filtering --> Application IDOC saved in the Database ---> Process IDOC immediately ---> Run tht Report prgm RPTEXTPT --> Read Process Code from Partner Profile -> Posting Module-->END.
I'm using the Business Object - BUS7011,
Tables Ptex2000,PTEX2010.
Do v follow the same scenario for the CATSDB to happen in both SAP instances.
I want the Basic Standard IDOC type v shall b using which is relevant to our scenario of Payroll and Time Sheet Management.
Plz let me know.
Any pointers will be much helpful.
ThankQ
Rohini.
[email protected]Solved myself.
-
Avoid the creation of idoc Debmas with Change Pointers
Hi everybody.
Ive customized the creation of idoc debmas with change pointers.
In BD64 I´ve defined the distribution model but Id like to avoid the creation of the debmas idoc when an specific user has created/modified the custumer data.
How can I get this?
RegardsHello,
I would suggest to handle this issue with authorization check...
check the authorization object using SU53 and add a separate role for those specific user excluding those objects...
Thanks
K. -
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
AhmadHey 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 -
Idoc Conversion rule, Change pointers and Filters
Hi Experts,
Please any one can help me out, i need material or clear picture about Idoc Conversion rule, Change pointers and Filters where we can use these concepts what is the befit for these concepts.
Thanks in advance,
Ramesh.Hi,
Check this link. It has got some of the tutorials you are looking for.
http://www.****************/Tutorials/ALE/ALEMainPage.htm
Cheers
VJ -
What is the IDOC type for changing PO price in ECC from SNC?
We have configured the consensus finding tolerance check for date and it is working. When we create confirmation from PO worklist by changing the price and the delivery date, it goes for manual approval if the date change is outside tolerance. Once the confirmation is approved by the buyer we are getting two Idocs in SAP. One is ORDRSP-ORDERS05. This one has the new price, but does not change the price in the PO. It only creates confirmation. The other one is PORDCH-PORDCH02. This one does not have the new price. It only changes the delivery date in the PO line item. We want one single IDOC which will change price (if price is changed), change delivery date and create confirmation. is that possible? If yes, what IDOC type would that be?
Thanks for your help.
SoumenHi Soumen
Can you please check whether the below settings are available on ERP side
SPRO-MATERIAL MANAGEMENT-PURCHASING-CONFIRMATIONS-SET UP CONFIRMATION CONTROL
select your confiramtion control line
lets say ZICH, select the confirmation sequence on left hand side
for your order acknowledgement,XX
check the field "Price"
and give the allowed tolerance values in fileds
Permitted Price Overrun in % (Inbound EDI/SOA)
Permitted Price Shortfall in % (Inbound EDI/SOA)
Now resend the data.... it will work
ORDRSP-ORDERS05 should work this time
Best Regards
Vinod -
Change pointers using ALE/IDOC configure
how configure CVhange Pointers using ALE/IDOC
Hi,
[Change pointers configuration|Change pointers]
For more info you can search in SCN, you will get more.
Thanks!! -
IDOC type DEBMAS06 change pointer
Hi,
I am working on idoc to file scenario.
I want to create/send idoc DEBMAS06.It is possible to send all segment of idoc using change pointer.
I am changing customer using XD02,and it send only 2 segment in idoc.There is require ment to pass all segment whenever there is any change in customer data.
Regards
MohitHi Rajesh,
Thanks for your reply.
I have tested bd12 and now it shows more segments then before.
But i need to send idoc automaticaly to pi system ,Is there any way to do so.
Right now i have activated chnge pointer and schedule back ground job RBDMIDOC to send idoc type debmas06 to pi system.
regards
Mohit -
Problem in Outbound Idoc Scenario with change pointers
Hi All,
I have a requirement where i have to create an outbound scenario, whenever i create or change in transaction PAL1 (Create Sales Representative), an idoc should be triggered.
i have created
- ZBasic idoc type
- ZSegments
And have assigned the ZBasic Idoc type to ZMessage type
Even I have maintained the fields to be triggered during change pointer in transaction BD52
Now my problem is, whenever i change a field in transaction PAL1 or create a new one, change pointer is not getting triggered via RBDMIDOC program.
Do we need to add an additional code to populate the Zsegments?
If so... can you send me the logic or Sample Code which fits my scenario?
Thanks.Satish,
you cna check this badi HRALE00OUTBOUND_IDOC
Thanks
Bala Duvvuri -
How to filter change pointers using BADI - BDCP_BEFORE_WRITE?
Hi,
We have a scenario where due to various loads lot of change pointers are getting generated. Now I want to delete the unwanted change pointers based on some condition.
Through this forum I figured out that we can use the BADI -> BDCP_BEFORE_WRITE and create an implementation in it to clear the change pointers based on our conditions.
But could anyone please tell me when does this BADI gets triggered? I tried various options by putting a break point in the implementation, in CHANGE_POINTERS_CREATE function module etc but couldnu2019t see my BADI getting called or triggered.
I have my code placed in the implementation of this BADI but doesnu2019t have any clue when it gets called. I assume being this a standard filter BADI it should be called of itu2019s own but how can I check whether my code works or not. Wonu2019t there be any Transaction code which when executed will trigger this BADI. Any help on this will be appreciated.
Thanks.Thanks again Amit. But still my question is at what event this BADI gets triggered.
Let me explain the code I have written.
LOOP AT change_pointers INTO lv_bdcpv.
lv_tabix = sy-tabix.
ws_c_objid = lv_bdcpv-cdobjid(18).
SELECT SINGLE cuobj klart obtab objek INTO t_inob FROM inob
WHERE cuobj = ws_c_objid AND
obtab NE 'KNA1' .
IF sy-subrc = 0.
DELETE change_pointers INDEX lv_tabix.
ENDIF.
ENDLOOP.
This is the code written so that I can get rid of all the change pointers that are written which are not relevant to Customer.
But I want to know how this BADI gets executed, at what event or at by which TCODE or program?? I tried to change some classification data and and it created entry in BDCPV but are not related to customer. So how can I get this BADI executed so that it deletes the entry from BDCPV table?
When I check the BDCPV table the entries are still there as unprocessed.
Hope I am clear with my question. Any help will be appretiated.
Thanks, -
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 WangI 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.
Maybe you are looking for
-
Error while running the RFC on ECC 6.0 server
Hello Champs, The problem I am facing while sending the data for validation and invalidation from RFC on ECC server to Pi server to be send to a webservice. This scenario was working perfectly fine when the RFC was run on R/3 4.7 server. On upg
-
Slide Pictures not displaying in Presenter- only text
Hi. I have just published my first powerpoint 2007 presentation using Presenter. The pictures on the slides are not displaying in the main window. They are only visible in the thumbnails. Any suggestions for fixes gratefully recieved.
-
Security Principal propagation from Web Server to App Server
How would I propagate a customer Principal from weblogic Web Server to a Weblogic App Server? For e.g this is what I want to do. 1. User logs in via a login page with UserId and password. 2. After a user is authenticated successfully, I want to fetch
-
OBIEE Issue - Physical Query not picking cascaded Conditions
In one the OBIEE Reports, I have given a set of NOT LIKE conditions as below: Session Name is not LIKE (pattern match) '%AUDIT%' AND Session Name is not LIKE (pattern match) '%audit%' AND Session Name is not LIKE (pattern match) '%Audit%' But when we
-
Down load ringtones from voice memos, Down load ringtones from voice memos
For use on iPhone 5c. If I make a voice memo of my. Grandson's voice how do I transfer it into a ringtone?