Mapping issue in quality system

Hi Experts,
I am new to BODS tool. Currently I am working with BODS 4.2 version.
I have an issue with mapping of datastores in quality system.
Actually I have created a project in Development system ( done all the things I mean to say Jobs, Workflows and Dataflows...).
For this project, Source tables are from SQL server and Target tables are from SAP BI system.
In BODS Development system, this project is working fine ( Source tables are perfectly mapped to Dev SQL Server Database tables and Target tables are mapped to SAP BI Dev system). While running a process chain in SAP BI DEV system, It's working fine.
Now I have Transported this Project to BODS quality system through central repository.Everything related to this project ( I mean to say project, Jobs, Workflows and Dataflows ) got reflected in quality system.
Can anyone please let me know, how should I map the Datastores related to this project to the quality system ( I mean to say now all the source tables should point to SQL Server Quality system Database tables and Target tables should point to SAP BI quality system ).
Appreciate for your quick responses.

Hi Cris,
Please Edit your SQL datastore and BI datastroe in BODS and provide the Quality system username and password. For BI datastore please update ip aslo.
Steps for BI datastore:
Right click on your BI datastore and click Edit--->click advanced tab-->Edit-->refer below sreenshoot
Please provide your Quality system credential then -->click apply-->ok
Same procedure you can follow for SQL datasore.
Thanks & Regards,
Balamurugan G

Similar Messages

User Mapping issue with custom system

Hello,
We have an iView that allows user's to store credentials to a back end system. We have created a sytem for this, that stores custom values (not the default user / mappedpassword). The code snippet below is used:
mappingData = UMFactory.getUserMapping().getUserMappingData(systeme, user);
Map map = new HashMap();
map.put(BUSINESS_UNIT, bu);
map.put(RACF_USERNAME, username);
map.put(RACF_PASSWORD, passwd);
mappingData.storeLogonData(map);
This code has worked fine in both EP6 SP2, and with our migration to NW04 (now up to SPS17). However, when we upgraded to NW04s SPS12, I get the following error:
Exception: Doug Test - setCredentials: java.io.IOException: com.sap.security.api.UMException: Mapped backend user ID not specified.
If I add the following line to my code above, it works again:
map.put("user", username);
Any ideas on why I need to specify the user field in NW04s when I did not need to previously?
Thanks in advance for any help.

Doug,
the following link might be helpful for working with NW04s UserMappingData object.
<a href="https://help.sap.com/javadocs/NW04S/current/se/com/sap/security/api/umap/IUserMappingData.html">IUserMappingData - NW04S</a>
Regards,
Shubhadip

Issue in Process Controlled workflow for Shopping cart in Quality system.

Hello All,
I ahve configured a Process controlled workflow in SRM 7.0 with custom resolver, and I am facing an issue taht the Workflow works well in Development but in Quality the approvers are dropped after SC is ordered in Quality system.
The SC Workflow drops the approvers picked up from the Interface method /SAPSRM/IF_EX_WF_RESP_RESOLVERGET_AREA_TO_ITEM_MAP and IF_EX_WF_RESP_RESOLVERGET_APPROVERS_BY_AREA_GUID of BADI /SAPSRM/BD_WF_RESP_RESOLVER. The approvers can be seen in the shopping cart Approval preview Tab until the SC is ordered.
I have compared the OSS notes relevant for Workflow, all of them have been transported, Also I compared and checked general Workflow settings, BRF Config and Process level settings in Dev and Quality, everything is same.
Also while debugging; the approvers can be seen in the decision set table in the create_process_forecast method of class /SAPSRM/CL_WF_PROCESS_MANAGER.
Kindly let me know what else i can check to find the root cause.
Thank you in advance for help!
Regards
Prasuna.

Hello Vinita;
Thanks for the input and sorry for the not so "ASAP" reply;
From what I'm seeing in from your 2 screenshot, i strongly believe that the problem is even before the Z implementation /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_APPROVERS_BY_AREA_GUID (in which the FM i ZSRM_GET_USER_FROM_PGRP is called. I think the problem could be in the process level determination ZSRM_WF_BRF_0EXP000_SC_APP100. Let me explain:
In your cases where not buyer is determined, in the approval tab there is not even a process level for buyer approval. If the problem were indeed in the implementation /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_APPROVERS_BY_AREA_GUID then the process level would be there, but the system will display, instead of the name of the buyer(if the buyer determination fails) a red label with the message: "With the strategy "Buyer determination" an approver could not be determined (or something like that..please check the image at the end of the text)".
I can propose a way to discard this: Implement the method /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_FALLBACK_AGENTS of class ZCL_BADI_SC_WC (in case you didn't know, in this method you can specify an "default" approver in case that the determination of approver in GET_APPROVERS_BY_AREA_GUID fails). The idea is to specify an default approval and see how it behaves:
If the user you indicated in the method GET_FALLBACK_AGENTS appears as approver, then yes, the problem is arises from implementation GET_APPROVERS_BY_AREA_GUID, in which case it could be a data problem (peharps in pposa_bbp?). You could also check in TX SU53 with the users with this problem to see if there's a missing authorization objetc.
If, in the other hand, the "default" approver is not shown, it means that the process level buyer determination is not even called, so you should check in more detail ZSRM_WF_BRF_0EXP000_SC_APP100 and /SAPSRM/CL_WF_PROCESS_MANAGER > Determine process restart –method ----- (i have never used this method, so i could not tell if it could be the source of the problem).
Also, you could implement the method GET_FALLBACK_AGENTS in this way so the default approver would be the WF administrator indicated in the customizing (or you could just append directly any user you want):
METHOD /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_FALLBACK_AGENTS.
   DATA: lv_admin_expr TYPE swd_shead-admin_expr,
         lv_admin      TYPE swd_shead-wfi_admin,
         lv_admin_type TYPE sy-input,
         ls_agent      TYPE /sapsrm/s_wf_approver.
   CALL FUNCTION 'SWD_WF_DEFINITION_ADMIN_GET'
     IMPORTING
       default_admin_expr = lv_admin_expr
       default_admin      = lv_admin
       default_admin_type = lv_admin_type.
   ls_agent-approver_id = lv_admin.
   APPEND ls_agent TO rt_agent.
ENDMETHOD.
Error of agent determination:
Please let me know the result of the test with the implementation of method GET_FALLBACK_AGENT. By doing this we could ensure if really the problem is in method GET_APPROVERS_BY_AREA_GUID or before. I just made the test in our system and I'm almost sure that you wont get the default approver, but i could be wrong.
Any question please let me know.
Best regards
Cristian R.

Issue while calling the RFC in SAP quality system but not in SAP Dev sys

Hi,
Our scenario is FIle-RFC-File.
We are calling the RFC from XI system in Development environment. This is working fine in Development environment, but not in Quality environment.
This changes are moved/transported to Quality environment in both XI and SAP side. But we are getting the following error in Quality system:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText><b>com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null></b></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please provide the inputs, what we can check at SAP side and XI side.
We have tried to test from XI Development to SAP quality environment, but we are getting the same error message.
Waiting for the precious inputs.
Thanks,
Ramesh.

Hi Ramesh,
This might be because your RFC adapter would not have been configured properly. Just do a check on it,in RWB(adapter monitoring) and activate it once more in ID.
Also check RFC comm. parameters such as host name/user id/password etc..
Also check whether your XML document is having a mismatch with your RFC XML.
Check with your payload ( from SXMB_MONI) and test it in your message mapping.
All the best!
cheers,
prashanth
P.S Please mark helpful answers

Mapping of Quality System (Source System) after the Transport

Hi,
We have two quality source systems like 300,400 in sync with the development ,to extract the data . I am transporting Transfer rule mapping from the development .After the transport to Quality , the changes are reflected in 300 . But I want to change it from 300 to 400 i.e.Transfer rule mapping should be reflected in 400. What is the transaction code used to change this mapping in BW System?
Thanks for your time.
Thanks & Regards,
Raja

Raja,
When you transport - you have a transport mapping in your dev system that tells BI which system connects to which system in the QA system for instance
FLAT_FILE in DEV could be Z_FLATFILE in QA - accordingly the datasources are mapped. Also the transfer rules are source system specific which means that you change the source system - the transfer rules will have to be recreated.
Instead what I am asking you is to maintain the mappings for client 400 in DEV and then maintain the mappings as 400 - 400 in the qa system and then transport the same. If your dev systems are linked to QA300 and your mapping says QA400 the same will hold good.. however if you have QA300 in dev to be sent to QA as QA300 and then change the source system .. it will not work since this will be seen as a source system change and you cannot change the same. You could try BDLS and try changing the logical client name ( I am not sure if it is BDLS ) or change the RFC connection parameters in SM59 but am not sure if it would work....

Issue whilel transporting from production system to quality system

Hi All,
    I am facing issue in process chain when I transport it from production system to quality system. Process chain is related to deleting PSA logs. When transported to quality system object_type and object_name fields in display variant becomes blank. In production system it is showing 8ZXXX_CA, it should become 8ZXXX_HA in quality system.
   Thanks for your help.
Regards,
Shankar

Hi,
    sorry it was frm dev system to quality system, not prod to quality.
Regards,
Shankar

Interactive Reports Issue Quality System

Hi experts,
This is regarding Interactive reporting fucntionality available in SAP CRM 7.0
I have configured this fucntionality in our DEV environment & actually created the various types of reports by assigning 10 custom fields which have z extensions.
Now, i have transported every custom field to Quality System but while creating a report, & while selecting the fields, i am unable to see those custom fields which i use to see in DEV box. I can only see the standard field
I would appreciate if someone can suggest or give some solution on this in order to fix in our Quality box.
Thanks & Regards,

>
SAPRPT wrote:
> Now, i have transported every custom field to Quality System but while creating a report, & while selecting the fields, i am unable to see those custom fields which i use to see in DEV box. I can only see the standard field
Hi!
Provided you created the extension fields with the Application Enhancement Tool, you will have to transport the enhancement into your target system first. Then generate it locally with report AXT_EXT_ACTIVATE_LOCAL.
Regards,
Sven Kriebel

Transporting issue from Developement System to Quality System

Hello Experts,
We are facing a problem in which address details in developement system are getting displayed and when the same code is transported to the quality system then the address fields are not getting displayed.
While debugging we found out that there is a variable which is calling the view (responsible for displaying address fields) in the developement system but the same view is not called in the Quality System.
We tried all sorts of backtracking but could not find where the variable is getting the values from.
Kindly Guide.
Regards
Sanket Jain
Edited by: Jain Sanket on Mar 22, 2011 3:57 PM

Hi BW Star,
I am transporting a process chain for deleting ODS change log from dev system to quality system. It is working fine in the dev system, but when transported to quality system, its process variants becomes empty for all the included ods change log delete steps. object_type and object_name field in variant becomes empty.
Thanks for your help.
Regards,
Shankar

Mapping issue in QA

*Hai Experts!*
*I am facing an issue in Quality server. The scenario is SOAP to JDBC. Which is working fine in Development server. But in QA the mapping is not happening and the Following error is displaying in the Trace view.*
*Can any one help me in solve this issue.*
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"><Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
<Trace level="1" type="T">Party normalization: sender </Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external = </Trace>
<Trace level="1" type="T">Sender party normalized = </Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST"></Trace>
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS">
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_INT_PID: SAP_CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
</Trace>
<Trace level="1" type="T">system-ID = OXQ</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2011-08-09T05:06:42Z CET </Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE"></Trace>
<Trace level="1" type="T">Message-GUID = 5EE4A690C24511E08056E41F1320CC6A</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC">
<Trace level="1" type="T">Queue name : XBTI0007</Trace>
<Trace level="1" type="T">Generated prefixed queue name = </Trace>
<Trace level="1" type="T">Schedule message in qRFC environment </Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK! </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message </Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking </Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST </Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC </Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye ! </Trace>
<Trace level="1" type="T">----
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST">
<Trace level="1" type="T">--start determination of sender interface action </Trace>
<Trace level="1" type="T">select interface ShipmentAdvice_iOlam_OUT_ASYN_SI </Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:ShipmentAdvice::iOlam:OPS:10 </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
</Trace>
<Trace level="1" type="T">Exception from packaging: No messages for constructing a package available.</Trace>
<Trace level="1" type="T">Continue single processing </Trace>
<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>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = OXQ</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2011-08-09T05:06:42Z CET </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace>
<Trace level="1" type="T">>>>PID delete old pid determination coding </Trace>
<Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV">
<Trace level="1" type="T">Reading sender agreement </Trace>
<Trace level="1" type="T">Inbound validation by Integration Engine does not take place </Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N </Trace>
<Trace level="1" type="T"> Cache Content is up to date </Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
</Trace>
<Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N </Trace>
<Trace level="1" type="T"> Cache Content is up to date </Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace>
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV">
<Trace level="1" type="T">number of receivers: 2 </Trace>
<Trace level="1" type="T">Multi-receiver split case </Trace>
<Trace level="1" type="T">Persisting initial (pre-split) message </Trace>
<Trace level="1" type="T">Persisting split messages (split kids) </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Splitting loop start </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Split Induced Change EO -> EOIO with QId: XI_SERIALIZE0000</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBQO3___</Trace>
<Trace level="1" type="T">Persisting split kid = 4E4085AB74480E30E1008000C0A8004E</Trace>
<Trace level="1" type="T">Generated prefixed queue name = </Trace>
<Trace level="1" type="T">Schedule message in qRFC environment </Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK! </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST">
<Trace level="1" type="T">--start determination of sender interface action </Trace>
<Trace level="1" type="T">select interface ShipmentAdvice_iOlam_OUT_ASYN_SI </Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:ShipmentAdvice::iOlam:OPS:10 </Trace>
<Trace level="1" type="T">--start determination of receiver interface action </Trace>
<Trace level="1" type="T">Loop 0000000001 </Trace>
<Trace level="1" type="T">select interface ShipmentAdvice_OPS_IN_ASYN_SI </Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:ShipmentAdvice::iOlam:OPS:10 </Trace>
<Trace level="1" type="T">--start determination of sender interface action </Trace>
<Trace level="1" type="T">Hence set action to DEL </Trace>
</Trace>
<Trace level="1" type="T">Split Induced Change EO -> EOIO with QId: XI_SERIALIZE0000</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBQO3___</Trace>
<Trace level="1" type="T">Persisting split kid = 4E4085AC74480E30E1008000C0A8004E</Trace>
<Trace level="1" type="T">Generated prefixed queue name = </Trace>
<Trace level="1" type="T">Schedule message in qRFC environment </Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK! </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST">
<Trace level="1" type="T">--start determination of sender interface action </Trace>
<Trace level="1" type="T">select interface ShipmentAdvice_iOlam_OUT_ASYN_SI </Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:ShipmentAdvice::iOlam:OPS:10 </Trace>
<Trace level="1" type="T">--start determination of receiver interface action </Trace>
<Trace level="1" type="T">Loop 0000000001 </Trace>
<Trace level="1" type="T">select interface ShipmentAdvice_iOlam_IN_ASYN_SI </Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:ShipmentAdvice::iOlam:OPS:10 </Trace>
<Trace level="1" type="T">--start determination of sender interface action </Trace>
<Trace level="1" type="T">Hence set action to DEL </Trace>
</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Splitting loop end </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to Call qRFC for execution of split kids ... </Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye ! </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace>
<Trace level="1" type="T">--start determination of sender interface action </Trace>
<Trace level="1" type="T">select interface ShipmentAdvice_iOlam_OUT_ASYN_SI </Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:ShipmentAdvice::iOlam:OPS:10 </Trace>
<Trace level="1" type="T">--start determination of receiver interface action </Trace>
<Trace level="1" type="T">Loop 0000000001 </Trace>
<Trace level="1" type="T">select interface ShipmentAdvice_OPS_IN_ASYN_SI </Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:ShipmentAdvice::iOlam:OPS:10 </Trace>
<Trace level="1" type="T">--start determination of receiver interface action </Trace>
<Trace level="1" type="T">Loop 0000000002 </Trace>
<Trace level="1" type="T">select interface ShipmentAdvice_iOlam_IN_ASYN_SI </Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:ShipmentAdvice::iOlam:OPS:10 </Trace>
<Trace level="1" type="T">--start determination of sender interface action </Trace>
<Trace level="1" type="T">Hence set action to DEL </Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST"></Trace>
</SAP:Trace>
Regard's
Preethi
Edited by: preethi_malu on Aug 9, 2011 7:59 AM

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Party normalization: receiver</Trace>
<Trace level="1" type="T">Receiver scheme external =</Trace>
<Trace level="1" type="T">Receiver agency external =</Trace>
<Trace level="1" type="T">Receiver party external =</Trace>
<Trace level="1" type="T">Receiver party normalized =</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS">
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_INT_PID: SAP_CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">system-ID = OXQ</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2011-08-10T08:23:48Z CET</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = BE8DFF410EFD44533BEDA93E4E7FD402</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC">
<Trace level="1" type="T">Queue name : XBTI0006</Trace>
<Trace level="1" type="T">Generated prefixed queue name =</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST">
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface dealTicket_OPS_OUT_ASYN_SI</Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:DealTicket:OPS:iOlam:20</Trace>
<Trace level="1" type="T">--start determination of receiver interface action</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">--start determination of sender interface action</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">Exception from packaging: No messages for constructing a package available.</Trace>
<Trace level="1" type="T">Continue single processing</Trace>
<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>
<Trace level="1" type="T">system-ID = OXQ</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2011-08-10T08:23:48Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>
- <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV">
<Trace level="1" type="T">Reading sender agreement</Trace>
<Trace level="1" type="T">Inbound validation by Integration Engine does not take place</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="1" type="T">number of receivers: 2</Trace>
<Trace level="1" type="T">Multi-receiver split case</Trace>
<Trace level="1" type="T">Persisting initial (pre-split) message</Trace>
<Trace level="1" type="T">Persisting split messages (split kids)</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Splitting loop start</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Split Induced Change EO -> EOIO with QId: XI_SERIALIZE0067</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBQO0___</Trace>
<Trace level="1" type="T">Persisting split kid = 4E42267021350B00E1008000C0A8004E</Trace>
<Trace level="1" type="T">Generated prefixed queue name =</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST">
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface dealTicket_OPS_OUT_ASYN_SI</Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:DealTicket:OPS:iOlam:20</Trace>
<Trace level="1" type="T">--start determination of receiver interface action</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface InterfaceCollection</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/XI/System</Trace>
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
</Trace>
<Trace level="1" type="T">Split Induced Change EO -> EOIO with QId: XI_SERIALIZE0067</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBQO0___</Trace>
<Trace level="1" type="T">Persisting split kid = 4E42267121350B00E1008000C0A8004E</Trace>
<Trace level="1" type="T">Generated prefixed queue name =</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface dealTicket_OPS_OUT_ASYN_SI</Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:DealTicket:OPS:iOlam:20</Trace>
<Trace level="1" type="T">--start determination of receiver interface action</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface dealTicket_OPS_IN_ASYN_SI</Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:DealTicket:OPS:iOlam:20</Trace>
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Splitting loop end</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to Call qRFC for execution of split kids ...</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>

Error while transporting database index into quality system

Hello,
I am getting an error while transporting a new index in quality system.
I have created a new index for table VBFA in TRD and activity the object without errors. I even adjusted the database table using database utility.
While transporting the request there was a strange error "R3TRTABLVBFA was repaired in this system".
I retransported the objects using a new request. However I still got the same error.
Please help.

Navin,
No idea about the error you have mentioned but check the SAP Notes 185530 and see if you can avoid creating an index.In this Notes it is clearly mentioned on how to use VBFA table without any performance issues.
K.Kiran.

WF not triggering in Quality System

Hi,
We moved the Workflow to Quality System, but the event is not triggering.The event linkage is active and workflow customizing has been done.The WF-Batch user is having SUPER user group.Kindly help on this issue.
Thanks,
Mohan

One reason were workflow is not triggered, WF and Event link not enabled.
Hope you are using BOR QMSM and triggering task for notification created in QM02,
1)     try to simulate with SWUE and check whether WF is triggered or not for a dummy task created in QMSM
2)     Check did you made WF Generic otherwise it will not trigger the WF
If you designate your workflow task as a "general task", this means that all users are authorized to start this task.
To restrict the number of authorized persons, you can assign the task to an object from the organizational plan (organizational unit, job, user,...). This is a general procedure and can be used with all types of tasks. If you assign the task directly to a user, only this person is authorized to start the task.
3)     check for user authorization
4)     Check for WF consistence swu5/swu4

Workflow Event is not triggering in Quality System

Hello
We developed workflow in DMS module for Status change of teh Change Number (Document NUmber) .It is working fine in dev system but not in Quality system .
Please provide valuable adivse on the same

This is weird you should ask for authorization in swel. If something is getting triggered in Dev and not in quality then there is something missing in Configuration. You have to get authorization for SWEL. Now how you get authorization that issue I cannot resolve. You check all the checkpoints for wflow triggering.
Thanks
Arghadip

Credit memo and MAP issue

Hello Guru's
I have 2 issues, and i am unable to understand the system logic for the same
Issue 1:-
We have an Intercomapny scenario
sequence of transaction is as follows
1. Create Return purchase order (document type NB) - Intercompany purchase
2. Post return goods receipts - movement type 161
3. Post credit memo with respect to return purchase order
4. Cancel the movement type 161 - using 161 movement type
System allows me to cancel the document created using 161 movement type
Step 4 should not be allowed but system is allowing me to do so, please advise how to stop this
Issue 2:-
I have a strange MAP issues which is flactuating very drastically
the scenario is as follows
Store stock is 10 ea, stock value is 1000, MAP is 100
DC map is 25
When we make return STO from store to DC, ths stocks are issued at DC MAP (condition type P101)
Assume we issue 9 quantity from Store then
Store stock is 9 ea, stock value is (1000-(25*9)) = 775, MAP is 775/1 = 775
This transaction is causing major flactuation in store MAP (100 changed to 775)
Please advise if there is any way we can control this behaviour
I understand that there is a setting which will in case of major MAP changes will put the amount into PRD account.
Appreciate if you can guide me to help
Regards
Amit

Hi,
For your first scenario,
for a retun po of IC NB type, after creating the PO you need to deliver the same at VL10G. For the delivery system will allow to create the PGR . Prior to these steps you need to return the goods using 161 at MIGO.Please check this 161 stock posted to stock in transit.After PGR system will clear the stock in transit.
Now after claring the stock from transit try cancelling the MIGO 161 document.
For the second query,
Please review your question' When we make return STO from store to DC, ths stocks are issued at DC MAP (condition type P101)
Assume we issue 9 quantity from Store then
Store stock is 9 ea, stock value is (1000-(25*9)) = 775, MAP is 775/1 = 775
This transaction is causing major flactuation in store MAP (100 changed to 775),
Please review the third line.
Regards,

Error while Replicating the Data Source in Quality System....

Dear Expert,
I have created a generic data source in R/3 Dev system and I replicated the data source to BW DEV system. Everything is fine in DEV system.
I have transported the Data Source to R/3 Quality System. And transported the related objects in BW DEV system to BW QUALITY system.
Now I am getting the error as follows :
BW QUA System --> RSA1 --> Source System --> Data source Overview --> Sales & Distribution --> _REPLICATE_
*DATASOURCE*.( clicked )
Its moving to another screen (R/3 QUALITY) , but it is coming as a LOGIN screen. Its askong for the USER name and Password. And when I click on BACK button , its givin following pop-up
RFC connection to source system LOGSYS is damaged ==> no Metadata upload
What could be the issue ?? Please suggest.
Thanks,
Sanjana

Hi saveen,
Yes I transported in that manner.
I checked in Source System ( RSA13):
Its giveng the pop-up ,
RFC connection check failed. Check connection
Please suggest, how can I proceed ?
Thanks,
Sanjana

Error in transporting the Transformation to Quality system

Hi All,
I am trying to transport the transformation which has field level routine as well as start and end routine.
I have basically ehanced the standard routine and it works perfectly fine in dev server . I have even loaded the data and generated reports on this cube.
Now i am trying to transport it to Quality system. It throws up some "syntax error in routine" error. Very strange.
All my routine in Dev is working but during transport ther is some issue.
i saw some post on same but they are suggesting to regenerate a new transformation. For me this will be a nightmare as there are so many routnies at field level and as end routine.
Kindly suggest how can i rectify this error.
Note:- I had generated this transformation via old update rules with Migration function.
Thanks & Regards,
Anup

Hi Anindya,
Below is my source code for one field level routine in transformation.
FORM routine_0080
TABLES
   p_monitor         STRUCTURE rsmonitor
USING
    COMM_STRUCTURE TYPE _ty_s_sc_1__rule_52
CHANGING
    RESULT         TYPE _ty_s_tg_1_full-srvclen
    RETURNCODE     LIKE sy-subrc
    ABORT          LIKE sy-subrc
RAISING
    cx_sy_arithmetic_error
    cx_sy_conversion_error.
* init variables
* fill the internal table "MONITOR", to make monitor entries
DATA: ultimo LIKE sy-datum.
IF g_record_no <> RECORD_NO.
    g_record_no = RECORD_NO.
    CLEAR: employee_wa, person_wa.
    CLEAR: employee_md, person_md.
ENDIF.
PERFORM read_md_employee
          USING    COMM_STRUCTURE-employee
                   COMM_STRUCTURE-calday
                   RECORD_NO
                   RECORD_ALL
                   SOURCE_SYSTEM
          CHANGING employee_wa
                   RETURNCODE.
employee_md = employee_wa.
PERFORM calculate_ultimo
          USING COMM_STRUCTURE-calday+0(6)
                 RECORD_NO
                 RECORD_ALL
                 SOURCE_SYSTEM
          CHANGING ultimo
                   RETURNCODE.
IF NOT employee_md-entrydate IS INITIAL.
    RESULT = ultimo+0(4) - employee_md-entrydate+0(4).
    IF ultimo+4(4) LT employee_md-entrydate+4(4).
      RESULT = RESULT - 1.
    ENDIF.
ENDIF.
* result value of the routine
* if the returncode is not equal zero, the result will not be updated
RETURNCODE = 0.
* if abort is not equal zero, the update process will be canceled
ABORT = 0.
p_monitor[] = MONITOR[].
CLEAR:
    MONITOR[].
CLASS lcl_transform IMPLEMENTATION.
METHOD compute_0AGE_RANGE.
*   IMPORTING
*     request     type rsrequest
*     datapackid type rsdatapid
*     SOURCE_FIELDS-CALDAY TYPE /BI0/OICALDAY
*     SOURCE_FIELDS-EMPLOYEE TYPE /BI0/OIEMPLOYEE
*    EXPORTING
*      RESULT type _ty_s_TG_1-AGE_RANGE
    DATA:
      MONITOR_REC    TYPE rsmonitor.
*$*$ begin of routine - insert your code only below this line        *-*
Data:
    COMM_STRUCTURE   type _ty_s_SC_1__RULE_20,
    l_subrc          type sy-tabix,
    l_abort          type sy-tabix,
    ls_monitor       TYPE rsmonitor,
    ls_monitor_recno TYPE rsmonitors.
data:
    l_monitor        type standard table of rsmonitor.
REFRESH:
    MONITOR.
* Runtime attributs
    SOURCE_SYSTEM = p_r_request->get_logsys( ).
    MOVE-CORRESPONDING SOURCE_FIELDS to COMM_STRUCTURE.
* Migrated update rule call
Perform routine_0070
TABLES
    l_monitor
USING
    COMM_STRUCTURE
CHANGING
    RESULT
    l_subrc
    l_abort.
*-- Convert Messages in Transformation format
    LOOP AT l_monitor INTO ls_monitor.
      move-CORRESPONDING ls_monitor to MONITOR_REC.
      append monitor_rec to MONITOR.
    ENDLOOP.
    IF l_subrc <> 0.
      RAISE EXCEPTION TYPE CX_RSROUT_SKIP_RECORD.
    ENDIF.
    IF l_abort <> 0.
      RAISE EXCEPTION TYPE CX_RSROUT_ABORT.
    ENDIF.
I am not able to change the code which are marked with " * ". Where can i change the code here?
Regards,
Anup

Mapping issue in quality system

Similar Messages

Maybe you are looking for