RFC Call: Missing namespace declaration
Dear experts,
I have a file to RFC scenario. I imported the RFC and create files exactly according to the RFC structure, so I don't use a mapping. When I create a file, it provides the following error in the adapter log:
<i>Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not get functionname from XML requst: com.sap.aii.af.rfc.RfcAdapterException: failed to read funtionname from XML document: missing namespace declaration(2)</i>
What do I need to do to fix this.
Thanks in advance!
This is the whole message:
I created my own interface and mapped it to the RFC:
This is the message. Now it successfully pass XI and the adapter sais it is delivered.
BUT nothing is seen in the target system... how is that possible???
<?xml version="1.0" ?>
<ns:MT_TO_CREATE xmlns:ns="urn://cchbc/w2/xi/mes/warehousetransfer">
<LGNUM></LGNUM>
<TIMEST>20071207094550.0000000</TIMEST>
<WERKS>4510</WERKS>
<ZLAST>0</ZLAST>
<ZSCID>SCANPRD4</ZSCID>
<I_LTAP>
<item>
<EAN11>5449000003096</EAN11>
<LETYP>E2</LETYP>
<VSOLM>48.000</VSOLM>
<LENUM>00345101239500010930</LENUM>
<VFDAT>2008-12-11T00:00:00</VFDAT>
<WDATU>2007-12-07</WDATU>
<ZLINE>830</ZLINE>
<ZTIME>09:43:32</ZTIME>
<BRGEW/>
</item><item>
<EAN11>2229000058744</EAN11>
<LETYP>E2</LETYP>
<VSOLM>48</VSOLM>
<LENUM>00000000003000002961</LENUM>
<VFDAT>2008-12-11T00:00:00</VFDAT>
<WDATU>2007-12-07</WDATU>
<ZLINE>830</ZLINE>
<ZTIME>09:44:01</ZTIME>
<BRGEW/></item><item>
<EAN11>2229000058744</EAN11>
<LETYP>E2</LETYP>
<VSOLM>48.000</VSOLM>
<LENUM>00000000003000002978</LENUM>
<VFDAT>2008-12-11T00:00:00</VFDAT>
<WDATU>2007-12-07</WDATU>
<ZLINE>830</ZLINE>
<ZTIME>09:44:32</ZTIME>
<BRGEW/></item></I_LTAP></ns:MT_TO_CREATE>
And the output is:
<?xml version="1.0" encoding="UTF-8" ?>
- <ns1:ZWM_TO_CREATE xmlns:ns1="urn:sap-com:document:sap:rfc:functions">
<LGNUM />
<TIMEST>20071207094550.0000000</TIMEST>
<WERKS>4510</WERKS>
<ZLAST>0</ZLAST>
<ZSCID>SCANPRD4</ZSCID>
- <I_LTAP>
- <item>
<EAN11>5449000003096</EAN11>
<LETYP>E2</LETYP>
<VSOLM>48.000</VSOLM>
<LENUM>00345101239500010930</LENUM>
<VFDAT>2008-12-11T00:00:00</VFDAT>
<WDATU>2007-12-07</WDATU>
<ZLINE>830</ZLINE>
<ZTIME>09:43:32</ZTIME>
<BRGEW />
</item>
- <item>
<EAN11>2229000058744</EAN11>
<LETYP>E2</LETYP>
<VSOLM>48</VSOLM>
<LENUM>00000000003000002961</LENUM>
<VFDAT>2008-12-11T00:00:00</VFDAT>
<WDATU>2007-12-07</WDATU>
<ZLINE>830</ZLINE>
<ZTIME>09:44:01</ZTIME>
<BRGEW />
</item>
- <item>
<EAN11>2229000058744</EAN11>
<LETYP>E2</LETYP>
<VSOLM>48.000</VSOLM>
<LENUM>00000000003000002978</LENUM>
<VFDAT>2008-12-11T00:00:00</VFDAT>
<WDATU>2007-12-07</WDATU>
<ZLINE>830</ZLINE>
<ZTIME>09:44:32</ZTIME>
<BRGEW />
</item>
</I_LTAP>
</ns1:ZWM_TO_CREATE>
Similar Messages
-
I am a novice at this and would like to get some suggestions from the gurus in this forum. I am trying to integrate an RFC call CTS_API_CREATE_CHANGE_REQUEST. But I do not see this RFC call using SE37. So I have two basic questions.
1) Is there a transaction that I can use to see a list of all RFC calls that are available in my R/3 system ?
2) Do I have to do anything to enable RFC calls, to be invokable from outside the SAP system ?
TIA
Yogi.Ok, I am posting this for the benefit of everyone.
I figured out a mechanism by which all RFC and BAPI calls within an R/3 system can be listed.
1) Invoke Transaction SE37
2) With the cursor on the 'Function Module' field press F4.
3) In the popup that shows , press the 'Information System' button on the task bar at the bottom. Its the one with the 'Binocular' graphic.
4) Another popup called "R/3 Repository Information System: Function Modules" opens up.
5) The third icon from the right of the task bar at the bottom reads "All Selections". It is a white icon, with a green mark and a black down arrow. Click on that.
6) You now get an advanced search screen with lots more options than the ones previously displayed.
7) One of the radio's says "RFC modules", another checkbox says "Only modules for BAPI".
8) Set whatever you are interested in and hit the "Check"
Enjoy.
Thanks,
Yogi -
"No Receiver Determined" in BPM Sync RFC Call
My scenario is xml file -> XI BPM -> RFC1 -> RFC2 (will call RFC2 if RFC1 is successful).
I am still just trying to get the RFC1 call working properly. I have been using blogs 1822, 1403 and 1926. I have also used some related BPM threads. It seems to be making the RFC call properly, but failing on the response.
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
These docs show my IB Repository and Directory setups. Can anyone look at them and tell me what is missing? Thanks in advance!
http://webpages.charter.net/kpwendel2/bsmDir.jpg
http://webpages.charter.net/kpwendel2/bsmRep.jpgKeith,
the problem is quite clear.
In your BPM, you have a synchronous interface in your sync send step.
However, in configuration, you have configured two asynchronous interfaces.
To be able to use sync send step in BPM, your RFC needs to be able to send a response back. Then you need to have two message mappings (one for bpm->rfc messages, and other for rfc_response -> bpm_response messages) and a interface mapping between the 2 sync interfaces (bpm_sync_int -> rfc_sync_int) using these 2 message mappings.
Also, some hints:
1. Don't do these mappings in BPM transformation step. You can execute them outside of BPM. Doing this, you will get better performance and also won't need to create abstract interfaces for RFC messages.
2. Use configuration wizard in Integration Directory (first, remove and reimport your BPM in Integration Directory). This way, you avoid different interfaces errors.
Regards,
Henrique. -
Retrieve namespace declarations from unmarshalled object
Hi,
I hope this is a beginner's question:
Still working on a web service, that uses an EJB for implementation. I'm using types/classes that were derived automatically from a WSDL (top-down/outside-in/what have you), or rather the corresponding schemata. I'm trying to retrieve namespace declarations from the unmarshalled object/element, but they are not contained in the "otherAttributes" [Map<QName, String>] member field of the respective object. However, I can retrieve any other attribute, qualified and non qualified, as long as the namespace isn't that of xmlns (http://www.w3.org/2000/xmlns/). For example:
Client:
MyElement my_element = new MyElement();
Map<QName, String> atts = my_element.getOtherAttributes();
QName ns_att = new QName("http://www.w3.org/2000/xmlns/", "a");
atts.put(ns_att, "http://www.example.com/");
QName test_att = new QName("test-att");
atts.put(test_att, "http://www.example2.com");
Service:
MyElement my_element = parent.getMyElement(); // ...
Map<QName, String> atts = my_element.getOtherAttributes();
for (QName qn : atts.keySet()) {
System.out.println("qn: ["+qn+"] value["+atts.get(qn)+"]");
This would print:
qn: [test-att] value[http://www.example2.com]
What am I missing? How do I get the namespace declaration? Thanks for your help in advance.
Cheers,
FelixI'll try to explain in a better way ...
I have a server with 2 different client and each client communicate to the server with a different interface.
My needs are to recognize from the server, the type of the client that are operating, and to do this I was thinking to recognize the interface used from the client to interact with the server
An other option is that, from the client, after retrieving the server and it's cast, a can call a method to pass to the server object, the type of the interface actually used.
But I think this makes a bit of nonsense because When I receive the marshalled object in my opinion doesn't make sense that i have to say the object it's type (the interface used).
the object is already alive and I think it has to know the interface used to refer it even if is on another VM
The cast operation doesn't store nothing into the current object instance?
local code example (I don't know if with JRMI the situation is different because the different JVM)
Map foo = new HashTable();
I need a method like
foo.curretUsedInterface() ... that return "Map"
instead of
foo.getClass().getName() that return "HashMap"
It's possible to obtain this information or I have to try another idea to make the server distinguish the client type?
thank you very much for your comprehension -
RFC call failed: JCO.Server could not find server function 'SET_SLD_DATA'
Hi, All
the system is PI 7.0 EHP1 oraclei Win2003 server, I configured SLD but I run RZ70, having error "RFC call failed: JCO.Server could not find server function 'SET_SLD_DATA' ". I know there are lot of tread about this error, but none of themsolve my problem. all JCO, RFC connections and SDL DATA supplier(VA) seem OK. error message in SM21 is "Could not send SLD data"
detail from SM21
The system could not send the data that has been collected automatical
for the System Landscape Directory (SLD). Check whether the gateway
configured in transaction RZ70 has been started and whether the SLD
bridge has been registered with this gateway.
You can use transaction SM59 to check this in the sending system for t
implemented RFC destinations. The RFC destinations have the standard
names "SLD_UC" for Unicode sending systems and "SLD_NUC" for non-Unico
sending systems. If a different RFC destination has been entered in
RZ70, check this destination instead.
You can use the Gateway Monitor to check the target gateways. In ABAP
systems, this monitor is started with transaction SMGW, or you can use
the external SAP program "gwmon". Check whether the specified gateway
has an active registration.
OF COURSE I checked RFC of SLD_UC and SMGW
any different ideas
Regards
ABHHi
Please check the following notes are implemented
Note 906454
Note 907729
You may be aware but if you are not --->RZ70 creates the required SLD* RFCs during runtime - therefore if you have defined these RFCs manually first using the same namespace you can get RFC conflicts which result in a failed submission
Please also check the user in the RFC is known to both systems and has required authorization to write to SLD
Generally with SLD you have to install or select a suitable gateway to handle incoming data supply traffic
Also the gateway you are using has be known to SLD and reflected in RZ70 - i.e these defintions have to be the same
It is also recommended to delete all references to SLD_* RFCs in data supplier and target SLD
after a failed submission attempt to allow RZ70 to recreate these consistently once the above has been checked
Best wishes
Stuart -
Message transfer between R/3 to XI By RFC call
Hi all,
I am trying to pass some parameters to XI by making an RFC call from R/3.In sm59 the connection is working fine with the RFC destination declared.I have created an RFC enabled function module and it has 5 import parameters .The FM doesn't contain any query as i have queried in the calling program. The program as followes;
DATA : IT_ZXIRFC LIKE ZXIRFC.
DATA: IS_BILL_NUM LIKE ZXIRFC-BILL_NUM,
IS_BUYERVATNUM LIKE ZXIRFC-BUYERVATNUM,
IS_BUYERACCNUM LIKE ZXIRFC-BUYERACCNUM,
IS_PRODUCTDES LIKE ZXIRFC-PRODUCTDES,
IS_BUYERNAME LIKE ZXIRFC-BUYERNAME.
SELECT * FROM ZXIRFC INTO IT_ZXIRFC
WHERE BILL_NUM = 'ABC1234'
AND BUYERVATNUM = 'CH456789'
AND BUYERACCNUM = 'THE456789'.
ENDSELECT.
IS_BILL_NUM = IT_ZXIRFC-BILL_NUM .
IS_BUYERVATNUM = IT_ZXIRFC-BUYERVATNUM.
IS_BUYERACCNUM = IT_ZXIRFC-BUYERACCNUM.
IS_PRODUCTDES = IT_ZXIRFC-PRODUCTDES.
IS_BUYERNAME = IT_ZXIRFC-BUYERNAME.
CALL FUNCTION 'ZRFC_XI_TEST1' IN BACKGROUND TASK DESTINATION 'SAP_X3ATEST'
EXPORTING
I_BILL_NUM = IS_BILL_NUM
I_BUYERVATNUM = IS_BUYERVATNUM
I_BUYERACCNUM = IS_BUYERACCNUM
I_PRODUCTDES = IS_PRODUCTDES
I_BUYERNAME = IS_BUYERNAME
COMMIT WORK.
I am getting notthing in moniter of XI when i excecute this program.
Please have a look at this and suggest me the solution.
Thank you,
Best regards,
Priya parmeshwar.Hi,
In SM59 my RFC destination is working fine.I have done the configuration according to Michal' blog
https://weblogs.sdn.sap.com/pub/wlg/1438.The [original link is broken] [original link is broken] [original link is broken] [original link is broken] RFC destination details as followes:
RFC destination : SAP_X3ATEST
Gateway Host : ld8022
Gateway service: sapgw22
Program Id : RFCTEST1
and here i have checked the Registered server program.
The same data has been updated in communication channel with a sender RFC adapter type.
Thankx,
Priya -
Hello,
I am setting up a very simple scenario where I am making a sychronous RFC call to a BAPI in R/3 (Version 4.6c) from an XI Sandbox (Version 7.0).
I have the RFC Communication channel properly configured, or so I think, and have verified everything else as well. I initiate the message from the Runtime Workbench and it shows with status "Successful" in the Message Monitoring section. However, when I look in SXMB_MONI transaction I am unable to find a response message from the BAPI coming back in the payload. I notice that even though the scenario is synchronous, the "Type" column in the SXMB_MONI transaction results shows it as "Asynchronous". Also, in the message details there is a Payload (which I am sending when I create and send the message from the RWB), in every step, until the Call Adapter step. After that there is no payload in the Call Adapter or the Response steps, just the SOAP Body with the Manifest.
In the message details I see that the <SAP:Processing Mode> entry is set to "Asynchronous" rather than "Synchronous".
Does anyone have any idea why this is so?
Thanks,
Murtaza.
Message was edited by:
Murtaza MadraswalaHi Amitabha,
I looked in the location you suggested and got a list of "Success" messages. These are listed below for you to look at:
Time Stamp Status Description
2007-06-18 15:17:54 Success Message successfully received by messaging system. Profile: XI URL: http://camapox1:50100/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER
2007-06-18 15:17:54 Success Using connection RFC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2007-06-18 15:17:54 Success Message successfully put into the queue.
2007-06-18 15:17:54 Success The message was successfully retrieved from the receive queue.
2007-06-18 15:17:54 Success The message status set to DLNG.
2007-06-18 15:17:54 Success Delivering to channel: GeneratedReceiverChannel_RFC
2007-06-18 15:17:54 Success MP: entering
2007-06-18 15:17:54 Success MP: processing local module localejbs/RfcAFBean
2007-06-18 15:17:54 Success RFC adapter received an asynchronous message. Attempting to send tRFC for Z_SD_RFC_ATP_WRAPPER with TID XIlc32S1tf4Togkm0mRWaHRG
2007-06-18 15:17:55 Success MP: leaving
2007-06-18 15:17:55 Success The message was successfully delivered to the application using connection RFC_http://sap.com/xi/XI/System.
2007-06-18 15:17:55 Success The message status set to DLVD.
The problem that I am seeing is that this is posted under the list of Asychronous Received Messages. Thats something I am just unable to understand. I have a Synchronous Outbound Interface defined and an RFC Communication Channel, which is Synchronous as far as I know. So why is the processing mode for the message being chosen as Asynch? Which config setting have I missed that is causing this problem? I am just unable to find the answer so far.
I appreciate your help. Please let me know if you have any clues.
Thanks,
Murtaza. -
SLD setup for UDF to RFC Call in XI
Hello,
I am trying to create a UDF that has an RFC Call to the XI backend and I have it working in my development system. But for some reason I cannot create the Business Service > Communication Channel > GeneratedReceiverChannel_RFC in my Assurance system.
I'm guessing it has something to do with a missing connection in my SLD but right now I can't see what could be missing. What do I need to create in the SLD to allow XI to appear as a business service?
Thanks,
MattHi
you dont need to do anything in SLD
follow this link
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70d90a91-3cf4-2a10-d189-bfd37d9c3231
infact there is another way (from what is explained in this doc), even without importing the RFC in IR/ ESR
more info
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40b64ca6-b1e3-2b10-4c9b-c48234ccea35
Regards
Vishnu -
Question on service userid - for RFC call
Hi
In XI 3.0 SP18 , we are making a RFC call from XI mapping runtime - to XI's ABAP stack - RFC function module . In the RFC receiver communication channel , I tried using service user XIISUSER , XIAPPLUSER for this RFC call - I got short dumps on XI ABAP stack mentioning that these two service users do not have authorization to make RFC calls -
Does anybody out there know what service user on XI has RFC call authorization that can used to make RFC calls onto XI ABAP stack from its mapping runtime ?
Correct answers will be rewarded rightaway. Thanks for your time in advance.Hi,
u have to make entry in sld...
Hi,,
2 Introduction
Configuring IDoc adapter in Exchange Infrastructure 3.0 requires some configuration on the SAP
systems, for both XI and the backend system where the IDoc message is to be sent. These steps, although
simple, are many times missed or mis-configured, causing the delivery of messages to fail.
Since IDoc adapter uses the ABAP stack, instead of J2EE, the configuration requirements are mainly in
ABAP.
Setting up IDoc adapters requires the XI integration server to be able to communicate with the backend
SAP system, and also to make sure that the Logical System Name used when posting IDoc exists on the
backend SAP system.
3 The Step By Step Solution
The basic steps for the IDoc configuration are outline below:
1. Configure SM59 on XI to communicate to SAP backend system.
2. Configure port on XI for IDoc communication.
3. Create or verify the Logical System Name on the SAP backend system.
4. Create or verify business system in XIs System Landscape Directory.
5. Verify the Logical System Name of the business system.
6. Verify or add the Logical System Name for the sender business system.
7. Create/configure the Communication Channel for the IDoc receiver adapter
3.1 Configure SM59 on XI to communicate to SAP backend system.
1. Using transaction SM59, create an RFC destination with Connection Type = 3.
In this example, the RFC destination name is NDVCLNT510.
2. Enter the logon information:
3. Test the connection by clicking on Testing connection and Remote logon.
Both must be successful.
3.2 Configure port on XI for IDoc communication.
4. Go to transaction IDX1 on XI, and create a port. In this example, the Port name is SAPNDV.
The Port name must be in the form of SAPxxx, where xxx is the system ID of the backend SAP
system.
The Client must be the client number of the backend SAP system.
Select the RFC Destination which was created in the previous step.
3.3 Create or verify the Logical System Name on the SAP backend system.
5. Enter transaction SALE on the SAP backend system.
6. Create or verify the Logical System Name. In our example, NDVCLNT510 is verified.
3.4 Create or verify business system in XIs System Landscape Directory.
The business system name for the SAP backend system must contain a valid Logical System Name. This Logical System Name is the one verified or created in the previous step.
7. In the System Landscape Directory, select the SAP backend business system. If one does not exist, then create the business system. Verify the Logical System Name.
3.5 Verify the Logical System Name of the business system.
8. In the Integration Directory, doubleclick on the business system (in our example, it is NDVCLNT510).
Navigate the menu:
Service Adapter Specific Identifiers.
If information is empty or incorrect, then it will have to be synchronized with the content of the System Landscape Directory. Follow the steps below for synchronization.
9. (Optional) Synchronization of the business system in Integration Directory to the business system in System
Landscape Directory.
Double-click on the business system in the Integration Directory.
Switch to Edit mode.
Select menu: Service Adapter-Specific Identifiers
10. (Optional) Within the dialog box, click on the button as indicated below to resynchronize.
11. (Optional) If the expected data from the System Landscape Directory is not updated, then the SLD cache may need to be cleared first.
3.7 Create/configure the Communication Channel for the IDoc receiver adapter.
15. In the Integration Directory, create an IDoc receiver communication channel.
The RFC Destination is from step 3.1.
The Port is from step 3.2.
NOTE:
There is no need to create an IDoc sender Communication Channel for XI. Instead, the backend SAP system must be configure to send the IDoc to XI.
4 Appendix
Transaction: IDX2
There are a couple of situation where IDX2 can be useful on the XI system.
1. When we want to test connection between the XI and SAP backend system.
2. When an IDoc has changed, and the meta data stored in XI needs to be update. When an IDoc is sent from the SAP backend system to XI, XI will first check to see if the meta data for the IDoc is already in its persistent cache. If not, then XI will use the configuration in IDX1 to retrieve the IDoc meta data from the backend system. If the
meta is already in cache, then it will NOT do so. Therefore, when an IDoc has changed, it is necessary to manually update the new meta data on XI, or delete it from the cache, so that the latest version can be retrieved. IDX2 is used for this purpose.
Go to transaction IDX2 and click on Create.
Enter the IDoc Type and the Source Port as defined in step #2. Click Continue.If successful, the following will show up. If error occurs, then the IDX1 configurations will need to be re-checked.
Reward points if find useful. -
Error with Asynchronous RFC call to JDBC
Hi all,
We are working on a scenarion where in we have to make an asynchronous RFC call to JDBC.
We have configured RFC sender adapter following this weblog
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
We have created data types only for the database as RFC does not require any data types.
And also we have created message types,message interfaces accordingly.
In Message Mappping,we mapped the export parameters of RFC to the access fields of database message type.
Also we have created sender agreement,interface determinations etc.... accordingly
And for sending RFC request asynchronously we followed this weblog
/people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
Once done with all the above steps we could able to trigger the RFC call and caught with the following errors in SXMB_MONI and no errors are seen in communication monitoring
SOAP Error:
+<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>+
+- <!-- Request Message Mapping+
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_curr_exg_mm2_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" /> <SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_curr_exg_mm2_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Also trace shows the following error thogh the interface determinations are properly configured
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface BAPI_EXCHRATE_GETCURRENTRATES*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:rfc:functions</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="1" type="T">----</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
the above errors are shown as part of request mapping..
Can any one please let me know what other configurations do we need to do?
I did not map the RFC import parameters,do we need to do that
Any help in this regard is really appreciated
Rgds,
SanthoshHi,
I am really happy to hear that the problem with mapping is resolved.
Now as per your requirment It needs to be aynschornous RFC--> XI ---> JDBC call. In XI you should map the RFC Export parameters to the traget structure of JDBC.
then the question is to how to trigger the RFC Function Module in R/3 to XI.
Plesae follow below steps to trigger it from SAP R/3
1. Create a RFC in the R/3 system
2. Configure the SM59 and Sender Communication channle as given in the Michal's blog. Also test if it is succesful.
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
3. Import the RFC in XI
4. Do the mapping to the target strucutre
5. Configure the JDBC receiver adapter
/people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
6. You can trigger the RFC from R/3 sytem by using
Async Call - in ABAP program use below syntax to call RFC. Here the export parameters will be passed on to XI which further have mapped to JDBC.
CALL Function "RFC Name" IN BACKGROUND TASK destination <sm59 destination>
COMMIT WORK.
Sync Call
CALL Function "RFC Name" destination <sm59 destination>
Thanks
Swarup
Edited by: Swarup Sawant on Jan 27, 2008 9:14 AM -
FILE to multiple BAPI/RFC calls
Hi,
I have one input source (CSV with about 100 rows) and I wish to call a custom rfc for each row in my spreadsheet. (The custom RFC has a single flat import structure as opposed to a table or anything complex).
I am struggling to do this in XI.
I assumed I needed to assign one source to multiple targets in the Message interfaces, but this errors on activation due to the RFC occurrence being set to 1.
Do I need to do the same trick as with IDOCS or am I missing the point somewhere?
I have read several threads and one in particular seems to indicate it is possible, but so far this has evaded me.
Re: BOM CREATION
Please could you point me in the right direction.
Thanks
AndrewAndrew,
You could read the CSV file into an Integration Process
Save the message in a multiline container (in your case 100 rows)
Create a block
Create another container to hold the single row defined within this block
Set the following for the block
<b>Step Name</b> eg SplitForRFC
<b>Mode</b> ParForEach
<b>Multiline Element</b> Multiline container defined above
<b>Current Line</b> Single line container defined above
The <b>Mode</b> 'ParForEach' acts like a loop
Then within the block create a synchronous Send step which calls your RFC
<b>Design</b>
I would question having to make 100 RFC calls
If possible change the design so that the RFC interface can accept multiple messages and the RFC logic to loop through them and process the messages one at a time
Regards,
Mike -
How to remove SOAP namespaces declarations in body content?
Hi!
I'm calling a WS with WS-Security without problems but when I extract the content the SOAP message's Body(the "business" part), the namespace declarations of the SOAP part (envelope, security, etc.) are present in the root element. However, any of this namespaces is referenced in the message that I extract.
I'm extracting the message inside the body like this
XmlObject[] aXml = xml.selectPath(##THE QUERY##);
return XmlObject.Factory.parse(aXml[0].xmlText(_opts));
Is there a way of getting rid of these declarations?
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
I've tried changing the XmlOptions (setSaveAggresiveNamespaces, setLoadSubstituteNamespaces, etc.) without success.
Thanks in advance!just use $body/* and you will have what u wanted.
-
Finding caller program in a RFC call
Hi experts,
We are having lots of CALL_FUNCTION_NOT_FOUND short dumps in one of our systems. The errors are caused because other systems call a function that does not exist, so the dumps are created.
What we would like to know is what program is doing these calls, since all we can see in the short dump is the caller system and the function it is trying to access, but not the exact program where the call is performed so we can fix the code.
Thanks in advance for your support.Sorry if this is too much of a wall of text, I can't find an "attach file" type feature.
ABAP runtime errors CALL_FUNCTION_NOT_FOUND
Occurred on 11.12.2006 at 10:04:34
Function module "Y_EF_DETERMINE_PICTURE" not found.
What happened?
The function module "Y_EF_DETERMINE_PICTURE" was called, but cannot be
found in the Function Library.
The current ABAP/4 program "SAPMSSY1 " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
The program "SAPMSSY1 " contains a CALL FUNCTION statement. The name
of the function module to be called is "Y_EF_DETERMINE_PICTURE".
No function module exists with the name "Y_EF_DETERMINE_PICTURE".
All function modules are stored in the Function Builder (SE37).
Possible reasons:
a) Wrong name specified. Particular attention should be paid
to upper/lower case and underscores ("_").
or
b) Transport error
c) In the case of an enqueue/dequeue module, the lock object
may not have been activated (ABAP Dictionary).
How to correct the error
Check the last transports to the R/3 System.
Is the program "SAPMSSY1 " currently being changed?
If an enqueue/dequeue module is involved, is the activation
of the lock object missing in the ABAP/4 Dictionary?
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"CALL_FUNCTION_NOT_FOUND"
"SAPMSSY1 " or "SAPMSSY1 "
"REMOTE_FUNCTION_CALL"
Function modules with names similar to "Y_EF_DETERMINE_PICTURE":
Y_EF_USEX_DETERMINE_TAX
Y_GF1_DETERMINE_RECTYPE
Y_GK_DETERMINE_PRCTR
Y_EF_USEX_PICTURE_SUBMIT
Y_EF_USEX_SHOW_PICTURE
Y_EF_RFC_PICTURE_POST
Y_GF1_DETERMINE_SBU
Y_GF_DETERMINE_VERSION
Y_GF_DETERMINE_DATE_PREVMON
Y_GF1_DETERMINE_CURRENT_PERIOD
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "46C"
Application server....... "sapgp1s"
Network address.......... "52.99.71.21"
Operating system......... "AIX"
Release.................. "5.3"
Hardware type............ "00C4449E4C00"
Database server.......... "sapgp1s"
Database type............ "DB6"
Database name............ "GP1"
Database owner........... "SAPR3"
Character set............ "en_US.ISO8859-1"
SAP kernel............... "46D"
Created on............... "Aug 26 2005 22:40:31"
Created in............... "AIX 1 5 0056AA8A4C00"
Database version......... "DB6_71 "
Patch level.............. "2113"
Patch text............... " "
Supported environment....
Database................. "DB6 06., DB6 07., DB6 08.*"
SAP database version..... "46D"
Operating system......... "AIX 1 4, AIX 2 4, AIX 3 4, AIX 1 5, AIX 2 5, AIX 3
5, , System build information:, -
, LCHN :
User, transaction...
Client.............. 000
User................ "SAPSYS"
Language............ "E"
Transaction......... " "
Program. ........... "SAPMSSY1 "
Screen. ............ "SAPMSSY1 3004"
Line of screen...... 2
Information about Remote Function Call (RFC) Caller:
System.............. "WP1 "
Database release.... "46C "
Kernel release. .... "46D "
Connection type. ... "3 " (2 = R/2, 3 = R/3, E = Extern, R = Reg.
Call type........... "S-" (S = synch., a/A = asynch., T = transactional
Client.............. 510
User................ "PC1706 "
Transaction......... "/COCKPIT/1 "
Function module..... "Y_EF_DETERMINE_PICTURE"
Call destination.... "GP1590"
Source server....... "wsdux44_WP1_10"
Source IP address... "52.99.71.124"
Additional information about RFC logon:
Trusted relationship " "
Logon return code... " "
Trusted return code. " "
Note: In Releases earlier than 4.0, some of the above information about
RFC calls may not be available.
Information on where termination occurred
The termination occurred in the ABAP/4 program "SAPMSSY1 " in
"REMOTE_FUNCTION_CALL".
The main program was "SAPMSSY1 ".
The termination occurred in line 67
of the source code of program "SAPMSSY1 " (when calling the editor 670).
Source code extract
000370 ENDMODULE.
000380
000390 MODULE %_RFCDIA_CALL OUTPUT.
000400 "Do not display screen !
000410 CALL 'DY_INVISIBLE_SCREEN'.
000420 PERFORM REMOTE_FUNCTION_DIACALL.
000430 ENDMODULE.
000440
000450 MODULE %_CPIC_START.
000460 IF SY-XPROG(4) = '%RFC'.
000470 PERFORM REMOTE_FUNCTION_CALL USING RFCTYPE_EXTERNAL_CPIC.
000480 ELSE.
000490 CALL 'APPC_HD' ID 'HEADER' FIELD HEADER ID 'CONVID' FIELD CONVID.
000500 PERFORM CPIC_CALL USING CONVID.
000510 ENDIF.
000520 ENDMODULE.
000530
000540
000550 FORM CPIC_CALL USING CONVID.
000560 COMMUNICATION SEND ID CONVID BUFFER HEADER.
000570 IF SY-SUBRC EQ 0.
000580 PERFORM (SY-XFORM) IN PROGRAM (SY-XPROG).
000590 ELSE.
000600 MESSAGE A800.
000610 ENDIF.
000620 ENDFORM.
000630
000640
000650 FORM REMOTE_FUNCTION_CALL USING VALUE(TYPE).
000660 DO.
CALL 'RfcImport' ID 'Type' FIELD TYPE.
000680 PERFORM (SY-XFORM) IN PROGRAM (SY-XPROG).
000690 RSYN >SCONT SYSC 00011111 0.
000700 ENDDO.
000710 ENDFORM.
000720
000730 FORM REMOTE_FUNCTION_DIASTART.
000740 DO.
000750 CALL 'RfcImport' ID 'Type' FIELD RFCTYPE_RFCDIA.
000760 PERFORM (SY-XFORM) IN PROGRAM (SY-XPROG).
000770 "Parking position for next request
000780 RSYN >SCONT SYSC 00011111 10.
000790 "ALternativ : Free mode
000800 "COMMIT WORK.
000810 "SYSTEM-CALL FREE MODE 0.
000820 ENDDO.
000830 ENDFORM.
000840
000850 FORM REMOTE_FUNCTION_DIACALL.
000860 SY-XCODE = '%_@no@'.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 1
SY-TABIX 0 SY-DBCNT 0
SY-FDPOS 0 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1
Chosen variables
Name.......................... Contents.1........2........3....+....4
SY-XPROG
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
SY-XFORM Y_EF_DETERMINE_PICTURE
554454454544445544555422222222
9F56F45452D9E5F093452500000000
%_SPACE
0
0
SY-MSGID
22222222222222222222
00000000000000000000
EBC_TO_ASC-X05 P&QéRêSëTèUíVîWïXìY~ZÜ[$*])^;_^
525E5E5E5E5E5E5E5E575D5252525355
06192A3B485D6E7F8C9EACB4CAD9EBFE
RFCTYPE_QUEUE 6
0000
0006
%_PRINT 000
2222333222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 0 ########
2222222222320000000022222222222222222222
0000000000000000000000000000000000000000
... + 120
22222222
0000000
SY-MSGNO 000
333
000
EBC_TO_ASC-X04 @ A BâC{DàEáFãGåHçIñJÄK.L<M(N+O!
424A4E474E4E4E4E4E4F4C4243424242
0010223B405163758791A4BECCD8EBF1
SY-MSGV1
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGV2
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGV3
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGV4
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
%_?NOT_ASSIGNED?
2222
0000
SPACE
2
0
SY-REPID SAPMSSY1
5454555322222222222222222222222222222222
310D339100000000000000000000000000000000
TYPE 3
0000
0003
SYST ########################################
0000000000000000000000000000000000000000
0001000000000000000000000000000000000000
... + 40 ########################################
0000000000000000000000000000000000000000
0000000000010000000100000000000000000000
... + 80 ########################################
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
... + 120 #######################################T
00000000
0000000
Active calls / events
No.... Type........ Name..........................
Programm
Include Line
1 FORM REMOTE_FUNCTION_CALL
SAPMSSY1
SAPMSSY1 67
2 MODULE (PBO) %_RFC_START
SAPMSSY1
SAPMSSY1 31
Internal notes
The termination occurred in the function "link_rfdir" of the SAP
Basis System, specifically in line 165 of the module
"//bas/46D/src/krn/runt/ablink.c#3".
The internal operation just processed is "CALY".
The internal session was started at 20061211100434.
Active calls in SAP kernel
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit = unlimited
=> Stack limit = unlimited
=> Core limit = 51200000
=> File size limit = unlimited
=> Heap address = 0x118dba360
=> Stack address = 0xfffffffffff5d50
=> Stack low = 0xfffffffffff5d50
=> Stack high = 0xffffffffffff600
=> Stack Trace:
AixStack() at 0x100059364
CTrcStack2() at 0x10005945c
rabax_CStackSave() at 0x10003959c
ab_rabax() at 0x1000425b4
link_rfdir() at 0x100540418
ab_link() at 0x100540a18
ab_rfcimport() at 0x1005f49f0
ab_jcaly() at 0x100024560
ab_extri() at 0x100487474
ab_xevent() at 0x10059c804
ab_dstep() at 0x10043bd98
dynpmcal() at 0x100942f94
dynppbo0() at 0x100941320
dynprctl() at 0x100948f40
dynpen00() at 0x1008f7818
Thdynpen00() at 0x1001429f4
TskhLoop() at 0x100146368
tskhstart() at 0x1001576ac
DpMain() at 0x100e06e38
main() at 0x100de72f4
List of ABAP programs affected
Type
Program
Gen. date time
LoadSize
Prg
SAPMSSY1
04.01.2000 19:06:59
20480
List of internal tables
No dump information available
Directory of application tables (contents)
Program
Name.......... Contents.1........2........3....+....
Directory of data areas (administration information)
Program
No.. Name.......... Lgth Ofsg Type Next Gen date Gen time
SYST
L not assigned -15 0 IN
M /%_LISTTABLE -14 1 CO 0
T global stack -13 1 2 GL 0
SAPMSSY1
A global data 0 3 DA
L constant dat 1 4 LI .0 .0216
L constant dat 2 5 LI SSY .0 .018B
L not assigned 3 6 IN
L SYST 4 7 TA 0
L SY 5 8 TA
L RSJOBINFO 6 9 TA
M /%_SYS%% 7 0 CO
M field symbol 8 1 FS
L TCPIC 9 2 TA
M field symbol 10 3 FS
L text pool 11 4 TP
Directory of data areas (contents)
Program
No.. Name.......... Contents..1........2........3....+....
SYST
L not assigned 0
L text pool 102 |SAPMSSY1
ABAP control blocks CONT
Include Line source code
Index Name F1 Co Par01 Par2. Par3. Par4. Tabl
SAPMSSY1 60 MESSAGE A800.
215 CLEA 00 84
216 CLEA 00 85
217 MESS 00 27
SAPMSSY1 62 ENDFORM.
218 ENDF 00
219 -
223 -
SAPMSSY1 65 FORM REMOTE_FUNCTION_CALL USIN
227 PERP 00 1
228 PERP 02
SAPMSSY1 66 DO.
229 WHIL 00 2
233 WHIL 00 3
237 BRAN 05 Branch to 251
SAPMSSY1 67 CALL 'RfcImport' ID 'Type' FIE
238 CALY 00 3 86 70 71 71
>>>>> CALY 02 87 P0
SAPMSSY1 68 PERFORM (SY-XFORM) IN PROGRAM
246 xper 02 12 13
248 PERP 80
SAPMSSY1 69 RSYN >SCONT SYSC 00011111 0.
249 SYSC 1F
SAPMSSY1 70 ENDDO.
250 BRAX 00 Branch to 233
251 WHIL 00 4
SAPMSSY1 71 ENDFORM.
255 ENDF 00
256 -
End of runtime analysis -
Namespace declaration inconsistencies
It has occurred to me that there is an inconsistency in the BPEL input message depending on where it is called from... If I test the BPEL process from the BPEL console using the test-form, the namespace of the input message is included. However, when the same BPEL process is called through another BPEL process (partner link), the namespace declaration is omitted.
This makes testing harder, since my XPath expressions will then either fail when I test from the BPEL Console, or when the process is invoked from another bpel.
The best way to fix it (I think) is to force the calling bpel process to include the namespace declaration when invoking the partner link. Is there a way to accomplish this?
Cheers,
BastiaanBastian
I have come across the same problem.
The BPEL Console is producing an XML message that is not consistent with the defined schema.
Has anyone else seen any other comments relating to this area - has it been raised as a bug?
I have included my message structures below.
BPEL Console Messsage - the namespaces in bold are the ones that are incorrect
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body xmlns:ns1="http://itv.com/parispublish">
<ns1:ParisPublishProcessRequest xmlns:ns2="http://itv.com/schemas/message/paris">
<ns2:ProgrammeAdviseRq>
<ns2:HeaderRq xmlns:ns3="http://itv.com/schemas/header/paris">
<ns3:RqUID>ABC</ns3:RqUID>
<ns3:Action>Add</ns3:Action>
</ns2:HeaderRq>
<ns2:Programme xmlns:ns4="http://itv.com/schemas/productcatalogue/paris">
<ns4:ProgrammeId>1234</ns4:ProgrammeId>
</ns2:Programme>
</ns2:ProgrammeAdviseRq>
</ns1:ParisPublishProcessRequest>
</soap:Body>
</soap:Envelope>
Partnerlink message - which is correct.
<inputVariable>
<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="payload">
<soap:Envelope xmlns="http://itv.com/parispublish" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header/>
<soap:Body>
<ProgrammeAdviseRq xsi:schemaLocation="http://itv.com/schemas/message/paris ../Message.xsd" xmlns="http://itv.com/schemas/message/paris" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<HeaderRq xmlns="http://itv.com/schemas/header/paris">
<RqUID>564</RqUID>
<Action>Add</Action>
</HeaderRq>
<Programme xsi:schemaLocation="http://itv.com/schemas/productcatalogue/paris ../productcatalogue.xsd" xmlns="http://itv.com/schemas/productcatalogue/paris">
<ProgrammeId>G/0002</ProgrammeId>
</Programme>
</ProgrammeAdviseRq>
</soap:Body>
</soap:Envelope>
</part>
</inputVariable> -
Duplicate namespace declarations when writing a file with JCA file adapter
I am using JCA File adapter to write a an XML file. The composite contains a mediator which received and transforms an XML to desired format and then calls a JCA file adapter to write the file.
The problem that I am having is that the written file has declaration of namespaces repeated with repeating elements instead of a single declaration at root. For ex.
instead of
<ns0:Root xmlns:ns0="namespace0" xmlns:ns1="namespace1" xmlns:ns2="namespace2">
<ns0:RepeatingChild>
<ns1:Element1>value1</ns1:Element1>
<ns2:Element2>value2</ns2:Element2>
</ns0:RepeatingChild>
<ns0:RepeatingChild>
<ns1:Element1>value3</ns1:Element1>
<ns2:Element2>value4</ns2:Element2>
</ns0:RepeatingChild>
</ns0:Root>What I see in the file is:
<ns0:Root xmlns:ns0="namespace0" xmlns:ns1="namespace1" xmlns:ns2="namespace2">
<ns0:RepeatingChild>
<ns1:Element1 xmlns:ns1="namespace1" xmlns:"namespace1">value1</ns1:Element1>
<ns2:Element2 xmlns:ns2="namespace2" xmlns:"namespace2">>value2</ns2:Element2>
</ns0:RepeatingChild>
<ns0:RepeatingChild>
<ns1:Element1 xmlns:ns1="namespace1" xmlns:"namespace1">>value3</ns1:Element1>
<ns2:Element2 xmlns:ns2="namespace2" xmlns:"namespace2">>value4</ns2:Element2>
</ns0:RepeatingChild>
</ns0:Root>So basically all the elements which are in different namespace than root element have a namespace declaration repeated even though the namespace identifier is declared at the root elment level.
Although, the XML is still valid, but this is unnecessarily increasing the filesizes 3-4 times. Is there a way I can write the XML file without duplicate declarations of namespaces?
I am using SOA Suite 11.1.1.4
The file adapter has the schema set as above XML.
I tried the transformation in mediator using XSL and also tried using assign [source(input to mediator) and target(output of mediator, input of file adapter) XMLs are exactly same].
but no success.I used automapper of JDeveloper to generate the schema. The source and target schema are exactly same.
I was trying to figure it out and I observed that if the namespaces in question are listed in exclude-result-prefixes list in xsl, then while testing the XSL in jDeveloper duplicate namespaces occur in the target and if I remove the namespace identifiers from the exclude-result-prefixes list then in jDeveloper testing the target correctly has only a single namespace declaration at the root node.
But, when I deployed the same to server and tested there, again the same problem.
Maybe you are looking for
-
In Safari how do I open a .PDF file in Preview instead of Adobe Reader?
When a pdf file opens on my computer in Safari, it opens with Adobe Reader (v. 7.0.8). Until recently, I could right-click on my mouse and and a drop-down menu would appear with the option to open the pdf file in Preview instead of Adobe. That option
-
Can I allow multiple users on a blog?
I would like to have remote users who can update and add pages to a blog in iweb. Is this possible?
-
Is it possible to use a campaign font when authoring an iBook rather than the standard font menu?
-
Color sampler onto curve layer?
I believe I knew how to do this but the brain cell that had the information must have died...... I BELIEVE I used to take the color sampler and put a sample on my image. Then I created a curves layer. AND, by holding some combination of shift/ctrl/al
-
Help installing flash detection express
I need some help installing the flash express detection script. Can anyone advise me on this? 1) This tutorial assumes that you have already added the Flash 8 detection scripts to a web page (as explained in the synopsis of the implementation process