IDoc to cXML using built-in SAP XSLT Processor

Hi ABAP experts,
i have a requirement to send an IDoc to an external system, the external system expecting it to be in cXML standard - without using XI/PI
has someone of you done this before?
I was looking at the option to utilize the built-in SAP XSLT processor (CALL TRANSFORMATION) since it supports XML to XML and ABAP to XML transformations
so the flow would either be
IDoc --> XSLT --> cXML (preferred)
IDoc --> XML (using XML port) --> XSLT --> cXML
is this possible?
Also, can the cXML be sent using the XML HTTP port in we21?
Your tips suggestions would be highly appreciated

Hello
Have you had a look at class CL_IDOC_XML1? This class does the transformation IDoc -> XML for you.
The next step would be to create the required XSLT transformation for the mapping IDoc-XML -> cXML.
Regards
Uwe

Similar Messages

Need to use Xalan in place of Oracle XSLT processor

We are working with Oracle BPEL 10.1.3.3. We have a requirement to use Xalan as the XSLT processor to preserve existing investment into transformation maps built using Contivo (which is certified to work with Xalan).
That said, we are having some trouble getting the Xalan processor to kick in going the java:exec route. For some reason, we end up with Oracle's XSLT processor in spite of asking for the Xalan implementation.
TransformerFactory tFactory = new org.apache.xalan.processor.TransformerFactoryImpl();
Transformer transformer = tFactory.newTransformer(new StreamSource(xslInURI));
System.out.println(tFactory.toString()+transformer.toString());
Strangely enough, the above snippet prints:
[email protected]Transformer@e39f6b
Wondering if anybody else has used Xalan successfully in conjunction with 10.1.3.3 bits. Appreciate your help.

please copy and paste the following in your xpath-functions.xml file
<function id="processXSLT" arity="2">
<classname>com.collaxa.cube.xml.xpath.functions.xml.GetElementFromXSLTFunction</classname>
<property id="namespace-uri">
<value>http://schemas.oracle.com/xpath/extension/xalan/xslt</value>
</property>
<property id="namespace-prefix">
<value>xalan</value>
</property>
</function>
This function would try to find the default transformer factory using
TransformerFactory.newInstance()
so you might need to place the xalan transformer factory properties file in the beginning of your classpath (server.xml ) or pass it as jvm system property like below:
-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl

Steps of EDI is used to transfer IDOC from R3 system to non sap system

Hi Experts,
Can you provide me Steps to configure EDI is used to transfer IDOC from R3 system to non sap system?
Full points will be assigned.
Thanks in advance!
Sapna

Hello,
         The EDI Configuration required to be done for Transfering IDoc to non SAP System is.
1. First of all, we need to identify the Transaction Data which is required to be Transfered to external System.(Ex: Sales Order Data or Shipment Data or Delivery Related Data).
2. Secondly, Identify the IDoc Type & Message Type. IDoc Type can be found in Transaction WE30 & Message Type Can be explored in Transaction WE81.
3. After that, assign the IDoc Type to Message Type in WE82.
4. Identify the Selection Program (Outbound) which is generally a Function Module in the Form of IDOC_OUTPUT_<Message Type>. Example, if the Message Type is ORDERS, the FM will be IDOC_OUTPUT_ORDERS.
5. Assign the Function Module to a Process Code in WE41 (Process Code for Outbound).
6. Configure Port Definitions in WE21 for which the RFC destinations are to be maintained in Transaction SM59.
7. Maintain Partner Profiles for the Outbound Message Processing in WE20.
8. Last, but not the Least, we need to Focus Mainly on Message Control Configuration which is nothing but maintaining the Output Type for the Outbound IDoc to be Triggered for the Sales Order Application or Delivery Application.
   i. In Message Control Configuration, we'll maintain
      a. Condition Tables
      b. Access Sequences
      c. Output Types
   ii. To Create the above elements, we can go to SPRO Transaction and do the same depending on the Application Area such as Sales / Shipping / Logistics Execution etc.
   iii. For Output Types & Access Sequences, we can go to the Transaction NACE or VK01 in which we'll maintain the Output Types / Access Sequences & Condition Records.
   Please note that all the above steps may not be needed if we are using some of the Standard Elements provided by SAP such as Message Type, Process Code, IDoc Type & Selection Program as many of the Standard SAP Applications have their own Elements for different Application Areas.
   For example, if you want to send an Order Confirmation IDoc when the Sales Order is saved, you can use the Message Type ORDRSP, IDoc Type ORDERS05 & Selection Program as IDOC_OUTPUT_ORDRSP.
   However, Message Control Configuration is the Key Factor and is required for all the Applications as per the Customer's / Client's Requirements.
Hope the above procedure was clear.
Thanks and Regards,
Venkat Phani Prasad Konduri

Using the XSLT processor for non-workbench XSLT

Hi there,
is it possible to use the built-in XSLT processor for arbitrary XSLT transformations which aren't checked in in the ABAP workbench but instead given as a runtime object (string or iXML)?
Instead of the built-in command CALL TRANSFORMATION which according to the doc is restricted to workbench transformations, I am looking for an option like this:
data: lo_transformation type ref to if_ixml_document,
      lo_source         type ref to if_ixml_document,
      lo_target         type ref to if_ixml_focument.
* I get lo_transformation and lo_source from somewhere out there
try.
    lo_target ?= cl_some_fine_class_which_i_am_looking_for=>transform(
                      io_source         = lo_source
                      io_transformation = lo_transformation ).
catch cx_xslt_runtime_error.
endtry.
Does anybody know such a feature?
For a background about this problem - in German language - see my blog
http://ruediger-plantiko.blogspot.com/2007/08/xslt-in-bsp-anwendungen-und-in-abap.html
Thanks and Regards,
Rüdiger

Dear Rashid,
thanks - this is the answer! I wonder why I didn't find this class one year ago. A little test prog shows that it works fine and even performant (about 0.5 millisec for creating the new dynamic XSLT program with the method set_source_stream( ) ). For usage in web apps, it would be nice to know whether the temporary program remains available in the application servers' buffer after end of process. I can't check this, since this is performed on the C/C++ level, and SE30 doesn't track the method set_source_stream() itself (it could show a decrease of runtime after the first call).
Here comes a little self-contained ABAP program to test the functionality. It works well on our system with SAPKB70012.
Thanks and regards,
Rüdiger
* --- Test usage of a dynamically given non-workbench XSLT program
report zz_test_cl_xslt_processor.
data:
* iXML master
go_xml type ref to if_ixml,
* iXML stream factory
go_sf type ref to if_ixml_stream_factory.
load-of-program.
go_xml = cl_ixml=>create( ).
go_sf = go_xml->create_stream_factory( ).
start-of-selection.
perform start.
* --- Start
form start.
data: lo_source    type ref to if_ixml_document,
        lo_result    type ref to if_ixml_document,
        lo_processor type ref to cl_xslt_processor,
        lv_p         type progname,
        lo_ex        type ref to cx_xslt_exception.
perform get_source changing lo_source.
create object lo_processor.
try.
* Set source
      lo_processor->set_source_node( lo_source ).
* Set result
      lo_result = go_xml->create_document( ).
      lo_processor->set_result_document( lo_result ).
* This could be time-critical, the creation of a dynamical XSLT prog?
      perform set_transformation using lo_processor
                                 changing lv_p.
* call xslt-proc
      lo_processor->run( lv_p ).
* Display result
      call function 'SDIXML_DOM_TO_SCREEN'
        exporting
          document    = lo_result
          title       = 'Result of Transformation'
        exceptions
          no_document = 1
          others      = 2.
    catch cx_xslt_exception into lo_ex.
      sy-msgli = lo_ex->get_text( ).
      message sy-msgli type 'I'.
endtry.
endform.                    "start
* --- Set XSLT transformation from stream
form set_transformation using io_processor type ref to cl_xslt_processor
                        changing cv_p type progname.
data: lo_trans     type ref to if_ixml_istream.
* sv_p contains temp. name of XSLT program after first call
statics: sv_p   type string.
if sv_p is initial.
* It seems that the name can be buffered on appserver level?
    import progname to sv_p
           from shared buffer indx(zx) id 'ZZ_TEST_XSLT_PROC'.
    if sv_p is initial.
      sv_p = 'X'.
    endif.
endif.
* Provide the stream containing the XSLT document (as a stream)
perform get_transformation changing lo_trans.
* Set transformation
io_processor->set_source_stream( exporting stream = lo_trans
                                   changing p      = sv_p ).
* Buffer progname on server - seems to work
export progname from sv_p
         to shared buffer indx(zx) id 'ZZ_TEST_XSLT_PROC'.
* string -> c move necessary, since xslt-proc-interface doesn't use
* the generic type csequence for program name
cv_p = sv_p.
endform.                    "set_transformation
* --- Parse a source given as string into an if_ixml_document
form get_source changing co_src type ref to if_ixml_document.
data: lv_s      type string,
        lo_stream type ref to if_ixml_istream,
        lo_parser type ref to if_ixml_parser.
concatenate
`<?xml version="1.0" encoding="iso-8859-1"?>`
`<countings filiale="2412" invnu="TIEFKUEHL SEPT.07">`
`<count recNum="1" gid="1" ean="59111828843" menge="1"`
`preis="0" recNumFrom="1"></count>`
`</countings>`
into lv_s.
* Eingabestream erzeugen und in if_ixml_document abbilden
lo_stream   = go_sf->create_istream_string( lv_s ).
co_src      = go_xml->create_document( ).
lo_parser   = go_xml->create_parser( document       = co_src
                                       istream        = lo_stream
                                       stream_factory = go_sf ).
lo_parser->parse( ).
endform.                    "get_source
* --- Put the transformation given as string into an if_ixml_istrean
form get_transformation changing co_trans type ref to if_ixml_istream.
data: lv_s   type string.
concatenate
`<?xml version="1.0" encoding="iso-8859-1"?>`
`<xsl:transform version="1.0"`
` xmlns:xsl="http://www.w3.org/1999/XSL/Transform"`
` xmlns:asx="http://www.sap.com/abapxml">`
`<xsl:strip-space elements="*"></xsl:strip-space>`
`<xsl:template match="countings">`
` <asx:abap>`
`   <asx:values>`
`     <SELOPT>`
`       <WERKS><xsl:value-of select="@filiale"></xsl:value-of></WERKS>`
`       <INVNU><xsl:value-of select="@invnu"></xsl:value-of></INVNU>`
`     </SELOPT>`
`     <COUNTINGS>`
`       <xsl:for-each select="count">`
`         <ZSRS_ZWSTI_LINE>`
`           <MATNR></MATNR>`
`           <EAN11><xsl:value-of select="@ean"></xsl:value-of></EAN11>`
`           <MAKTX></MAKTX>`
`           <MENGE><xsl:value-of select="@menge"></xsl:value-of></MENGE>`
`           <MEINH></MEINH>`
`           <UNAME></UNAME>`
`           <EXVKW></EXVKW>`
`           <WAERS></WAERS>`
`           <FF></FF>`
`           <GID><xsl:value-of select="@gid"></xsl:value-of></GID>`
`           <RECNUM><xsl:value-of select="@recNum"></xsl:value-of></RECNUM>`
`           <RECNUM_FROM><xsl:value-of select="@recNumFrom"></xsl:value-of></RECNUM_FROM>`
`           <REF_RECNUM><xsl:value-of select="@refRecNum"></xsl:value-of></REF_RECNUM>`
`         </ZSRS_ZWSTI_LINE>`
`       </xsl:for-each>`
`     </COUNTINGS>`
`   </asx:values>`
` </asx:abap>`
`</xsl:template>`
`</xsl:transform>`
into lv_s.
co_trans = go_sf->create_istream_string( lv_s ).
endform.                    "get_transformation
Edited by: Rüdiger Plantiko on Jul 4, 2008 10:25 AM

IDOC to XML using HTTP

Hi Friends,
Is there any possibilities to Convert IDOCs as XML using HTTP Adapter in SAP PI?
Because in my Scenario i need to send Idocs from ECC to Red Prariie using SAP PI.
Also is it there any possibilities using FTPS?
Please help me.
Thanks.

Hi PIstarter,
Sure this is possible. Just treat the IDoc like any other Service Interface that you use in the HTTP Receiver Adapter. You can even use the no-mapping approach if no additional processing is required by PI.
Hope this helps,
Greg

How to handle idoc documents by BizTalk without WCF-SAP Adapter?

Dear All,
our company is no customer of SAP.
But one partner company of us uses SAP Systems to generate business transactions like "INVOICE".
Then they send us such a idoc-file per email.
So I can not use the SAP-WCF Adapter by BizTalk (the download of SAP RFC SDK is constrained and only for customers) to generate a schema of such a flat file automatically.
The second problem: I believe that only the WCF Adpater can validate the structure of the infomartion in inbound idoc files.
Is there a way to solve this problem without using the WCF-SAP Adapter?
Thanks in advance

Actually I only need an idoc decoder and disassembler to import the information of the idoc file.
Is there a special pipeline component by MS?

Multiple IDocs to File using BPM

Hi All,
I have configured a scenario of multiple IDocs to file using BPM. In this scenario while I am triggering IDoc from R/3 system it is sent to the external program. I am getting in the status record of WE05 as IDoc is sent to an external system with status code 03. But I am unable to view the same message in moni of the XI system.
Also I have checked the ALE settings on both the sender and receiver side and it is fine.
Also in SM58 nothing is there in queue.
Can anyone solve this issue of mine?
Cheers,
Neethu.

Hi,
in many cases it's a problem with the RFC connection. You should try an authorization test in SM59 of the R/3 system.
This might also be useful:
http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/frameset.htm
Regards
Patrick

IDoc acknowledgement scenario using ALEAUD01 IDoc type

Hi All,
I have a query, regarding IDoc acknowledgement scenario using ALEAUD01 IDoc type as mentioned below.
In a scenario where we configure and send ALEAUD01 to sender as acknowledgement of the IDoc’s received, is there any way how do we make sure that IDoc’s received by target SAP system has sent the acknowledgement successfully. Would there be any key information in the ALEAUD01 IDoc, which refers to the IDoc/data sent?
Thanks
Rajendra

I needed 24 seconds to know the answer
I took the word ALEAUD01 into Google and added site:help.sap.com in the search field
Among the first 10 results was one with the subject
Acknowledgment Messages
one click to open and skimming through the text ....
And opening one of the other hits in Google told me even which field is having this info

How to create idoc and send it frm one sap to another sap

hi,
can anyone tell me the complete procedure of creating the idoc and sending it to another sap r/3
how to create rfc destination, partner profiles, port and outbound parameter and inbound parameter
thanks

Hi Azhar,
Go through the following Links
IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
Go through the following Steps for Creating IDoc Via ALE
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
        save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
   select all what ever you want and delete remaining fields.
   save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
   it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
   give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Regards
Sreeni

ORDERS05 IDoc to cXML SOAP - SOAP failing (Ariba call)

I am performing the following scenario:
I am sending an ORDERS05 IDoc from R/3 4.6 to XI. XI then maps the IDoc into cXML. I am then attempting to send the cXML via the SOAP adapter to Ariba via HTTP.
Everything works except the adapter fails when trying to send to Ariba. Here is the audit log:
2005-07-06 17:05:39 Success The message was successfully received by the messaging system. Profile: XI URL: http://myserver:50000/MessagingSystem/receive/AFW/XI
2005-07-06 17:05:39 Success Using connection AFW. Trying to put the message into the receive queue.
2005-07-06 17:05:39 Success Message successfully put into the queue.
2005-07-06 17:05:39 Success The message was successfully retrieved from the receive queue.
2005-07-06 17:05:39 Success The message status set to DLNG.
2005-07-06 17:05:39 Success Delivering to channel: cXML2Ariba
2005-07-06 17:05:40 Success SOAP: request message entering the adapter
2005-07-06 17:06:01 Error SOAP: error occured: java.io.IOException: failed to get the input stream from socket: java.lang.NullPointerException
2005-07-06 17:06:01 Error Exception caught by adapter framework: failed to get the input stream from socket: java.lang.NullPointerException
2005-07-06 17:06:01 Error Delivery of the message to the application using connection AFW failed, due to: failed to get the input stream from socket: java.lang.NullPointerException.
2005-07-06 17:06:01 Success The asynchronous message was successfully scheduled to be delivered at Wed Jul 06 17:11:01 UTC 2005.
2005-07-06 17:06:01 Success The message status set to WAIT.
Does anyone know what the error message means?
Could it possibly be that I am taking an Async IDoc, and posting a synchronous SOAP to Ariba?
Thanks!

Mary -
Hi I was wondering how you were able to determine that your XI server did not have internet connectivity and what you were able to do? We have a similar scenario only we are trying to use SSL for the connection with certificate AND getting the following error :
2005-09-08 15:46:31 Success The message was successfully received by the messaging system. Profile: XI URL: http://XIServer024:50700/MessagingSystem/receive/AFW/XI
2005-09-08 15:46:31 Success Using connection AFW. Trying to put the message into the receive queue.
2005-09-08 15:46:31 Success Message successfully put into the queue.
2005-09-08 15:46:31 Success The message was successfully retrieved from the receive queue.
2005-09-08 15:46:32 Success The message status set to DLNG.
2005-09-08 15:46:32 Success Delivering to channel: PCARD_Activate_File_Receiver
2005-09-08 15:46:32 Success SOAP: request message entering the adapter
2005-09-08 15:46:32 Error SOAP: error occured: java.lang.NullPointerException
2005-09-08 15:46:32 Error Exception caught by adapter framework: null
2005-09-08 15:46:32 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.

Extending the IDoc to cXML scenario

Hi Experts,
I have a scenario IDoc to cXML for sending ORDERS05 .
We got a requirement to develope a scenario by extending the Order header and line extention segements to include extra fields)of the IDoc used in the above scenario , hence I am doing the following
-Imported the extended IDoc into the Integration repository.
-Mapped the extra fields included to the target message.
-reloaded the IDoc Metada using IDX2.
As i am doing this as part of the other project please suggest on the following
--Explain the sections to be included in the Technical design document for XI configuration.
--configurations that I need to work on.
please do suggest any other things i need to work on to take the right approach.
Thanks in advance.
MK

Hi,
Nothing more u require in XI development when ever u are dealing with the Extended IDOC's.
Normal procedure as Standard IDOC's only.
If u are not able to view the extended IDOC's in the Repository means then u have to think the solution.
This problem is not there for u. so go a head with the normal procedure by importing those IDOC's in IR and do mapping as usual
Regards
Seshagiri

Idoc to cXML scenario

Hi,
I have a requirement (IDOC to cXML file), where i have to map PO IDOC to cXML file format. I understand from the cXML.org url that there are some DTD's freely available.
I guess the cXML file format is same as normal xml file with special format. please correct me if i am wrong.
can we use FILE adapter to convert the file to cXML file format. for example to abc.cxml.
can some one help me .
thanks.
azim

Hi Azias,
> Do we have to use third part adapter for this?
3rd party expression is usually used for Business Systems. Yes, you should create a 3rd party BS.
> can i use FTP adapter to create a file?
Yes
> what will be the extension of the file (i.e. abc.cxml)?
*.cxml
> Do we require secure connection in FTP adapter?
if you want to secure the connection / if you have sensible data
>
> If i want to post the cxml message to URL, then which adapter should is use? (HTTP/SOAP)?
http
Regards,
Udo

Use BPS in SAP BI

HI Gurus,
We are in New implementation, Our Client is looking to implement SAP BI, SEM BPS & BCS, SAP CRM & ECC
From a technical perspective we are a little confused. If any body can clarify some the question, it would be great
1) Is SAP BI supports SEM BPS? if supports can i use built BPS with BI or SEM BPS.
2) Is these two products ( SEM-BPS ) and BI-BPS essentially same or different... which is preferred?
Thanks
RAvi

SEM-BPS only comes when you install the SEM addon which you would be with SEM-BCS.
BW-BPS comes with BW 3.5 and BI 7.0 but the difference between SEM-BPS and BW-BPS is about 10 or so planning functions such as allocation, time lag, IRR, account based currency translation, etc. and some sample planning applicaitons which you can import from client 000 in SEM-BPS but not in BW-BPS.
Which versions does the client have for the different systems since that can have a slight impact. Oterwise bo
If you are using CRM, are you planning to use some of the CRM based planning stuff such as CRM markeing or TPM? If so, you need SEM-BPS from this as well.
IP is a newer planing product than BPS and has some additional strengths but it does not have the embedded planning services that SEM-BPS has.
BPC is the acquired OutlookSoft as a different product and there is a new version 7.0 coming out on BI 7.0 but please note that it uses different master data than BW so if you want integrated stuff with R/3, and CRM, you can have some challeges there.
Mary

What triggers idoc posting in outbound message from sap ?

Do change or create events can be used to trigger Posting to IDOC? Have any body used idoc for outbound message sending from SAP?

Hi Reddy,
Posting IDoc Packets
Two groups of function modules are used to post IDocs:
· Function modules which process IDocs in mass. These transfer packets of IDocs for which individual IDocs are updated in the same Logical Unit of Work (LUW).
· Function modules which process one IDoc per call.
· INPUTTYP contains the code for posting function modules.
To display the function module's INPUTTYP on the ALE Development screen, choose IDoc ® Inbound Processing ® Function Module® Maintain Attributes (BD51).
INPUTTYP can contain the following values:
· "0", for function modules which process IDocs in packets.
"1" and "2" for function modules which process one IDoc per call:
If you post the IDocs immediately, the SAP sending system determines the packet size. ALE inbound processing can recognize if the posting function module allows packet processing and if so, passes the IDoc packet to it. If not, the IDoc packet is split into individual IDocs.
If IDocs are posted in the background, you can specify the size of the IDocs to be generated in the program RBDAPP01.
If you use function modules that can process IDocs in mass, the database load is reduced.
If you group IDocs into packets, this may also be practical for function modules that post inbound IDocs one at a time, because the ALE layer calls the function module several times in the same dialog process, thereby reducing the administrative load on the SAP system.
If program RBDAPP01 carries out the background processing, as a guide, you should use a packet size of between 20 and 100 IDocs.
Packet processing and parallelism complement one another. Packet processing and parallelism complement each other, although in some situations they may compete with each other. If the size of the packet is too big, this may mean that not all the available dialog processes are being used.
Scheduling IDoc Posting
There are two ways of posting IDocs in ALE inbound processing:
·        Immediate processing:
Upon receipt inbound IDocs are immediately released for posting. ALE inbound processing splits the IDoc packets into individual IDocs.
·        Background processing
Inbound IDocs and IDoc packets are first saved in the database. IDoc packets are split into single IDocs beforehand.
The program RBDAPP01 later releases the saved IDocs for processing. Single IDocs can be put into packets and then processed.
Perform the following steps:
1.       Set-up background processing (IDoc/ALE area menu):
IDoc Interface/ALE ® Administration ® Runtime Settings ® Partner Profiles (WE20)
Then the required setting is: In the detail screen Inbound Parameters select the option Trigger by background program.
2.       Schedule posting (ALE customizing):
Transaction SALE ® Set-Up System Monitoring ®
         Posting IDocs in Recipient System ®Schedule
You can also process the IDocs manually by passing them to the posting function module. In ALE Administration choose Monitoring ®Status Monitor (BD87), select the IDocs and then select Process.
Regards,
Kumar.

Crystal report using ABAP from SAP ECC6.0 EHP 3.0

Hi Gurus,
Can i create crystal report using ABAP in SAP ECC 6.0 EHP 3 . as i am not able to see this link in SPRO.
IMG > SAP NetWeaver > Application Server > SAP List Viewer > Maintain SAP GUI Specific Settings.
Kindly guide me urgently.

http://help.sap.com/saphelp_slc/helpdata/en/27/c9ee1951fc4fb9ac322ac7e6fa7372/content.htm
If I understood your question correctly.
Have a look in the link above.
It is possible to use Crystal Reports from ALV.
Tammy Powlas also has some good guides on how to do this.
The ABAP however is not covered that much.
Best Regards
Ingrid

IDoc to cXML using built-in SAP XSLT Processor

Similar Messages

Maybe you are looking for