Regenerating ports for Partner Profiles and Source System (RSA1)

Hello all you SAP gurus,
During a recent backcopy we have an issue after updating Logical System names using BDLS. This has updated the Partner Profiles (WE20) correctly.
BUT
These partner profiles are trying to use ports (WE21) that have been mistakenly deleted. But if we try to recreate the ports we get the message
-"Choose another name! Name range reserved!"-
This specific port is referenced in outbound parameters. Perhaps this is stopping the change?
We could create new ports and hook them up to the partner profiles, but I'm concerned that there might be other locations where the deleted ports are referenced.
Any help would be greatly appreciated!

Hi J,
You can try and disconnect and re-connect the BW System to R/3. That would force the recreation of the Partner Profile.
Take a look at the connection data in table RSBASIDOC, write down the parameters, especially the IDoc Type.
In SE37, run function RSAP_BIW_DISCONNECT_40 and specify parameters for BW System.
Then run RSAP_BIW_CONNECT_40 and specify those parameter again for the BW System.
This will recreate the Partner Profiles. Then check the assigned ports and see if you still have the same issue. Just make sure the RFC connection is set correctly and working in SM59 before doing all this.
In any case, you can create new ports in WE21 and allow the system to assign the numbers automatically and you won't have any issue.
Hope it helps.
Regards,
Luis
Edited by: Luis Sales on Mar 18, 2008 7:28 PM

Similar Messages

No PSA for Infosource X and source system Y. Here Y is the flat file source

Hi,
We are facing an issue while transporting from dev s/m to quality. There is no PSA for Infosource X and source system Y. Here Y is the flat file source system this issue we are getting while transporting transfer rules.We are checked in OSS notes 518426. Its not helpful.
Thanks
Manjula

Hi
Try RS_TRANSTRU_ACTIVATE_ALL (SE38).
You may also check SAP Note 861890 - ODS tables disappear during the upgrade -
and activate all ODS Objects before the upgrade and run the program RSDG_ODSO_ACTIVATE.
also that with Stack 14 an extended version of this program is available together with the
Program RSUPGRCHECK. If errors occurs, consult also SAP Note 518426 and run transaction
RSSGPCLA for the regeneration of the RSDRO_* Objects.
Recheck whether you have Exported with correct parameters or not -- Try to Re Export the Same with all necessary objects .
Try Note 524554 and 325525 also
Hope it helps and clear

There is no PSA for InfoSource 8ZCCA_O09 and source system BWPCLNT800 RSAOD

Hi All:
We make a Heterogeneous system copy of BW 3.5. from Solaris 9-Oracle 9i to AIX 3.5-Oracle 9i.
We must have to rename the Logical System Name and during the Functional Testing the users configured the conections again in RSA1 transaction, then they start the
testing phase but get the next error in the Monitor-Administrator Workbench:
"@5C@ 28.02.2008 19:59:31 There is no PSA for InfoSource
8ZCCA_O09 and source system BWPCLNT800 RSAODS 203"
We can see that the errors refers to the old (BWPCLNT800) Logical
System Name; during the configuration of the RSA1 they renamed the
Logical System Name of the BW System to BWNIUSA800.
We found the SAP Note 518426 but we are not sure about if we can
execute it without affecting the system or the configuration.
Some one Can help us ?.
Best Regards
Reynaldo Rebolledo.

Hi Reynaldo,
this forum here is related to SAP NetWeaver Master Data Management. Your question seems to be related to SAP BI. Please raise your question in the [BI Forum|/community [original link is broken];, because I do not think that you'll find the experts to answer your question here.
BR Michael

There is no PSA for InfoSource ZOUTNBR_TEXT_CC and source system PCFILE

Hi All
The above subject line shows the error.
I have a custome data source in Development that is ZOUTNBR_TEXT which has a source system PC file.(flatfiles)
when i transported all transfer structures and data sources from Development to Quality, only my transfer rules were not activated. but when i manually activated in Quality it throws with an error
There is no PSA for InfoSource ZOUTNBR_TEXT_CC and source system PCFILE
Please let me know how can i activate my transfer rules.
Archana

Hi,
We also faced the same issue while transporting from dev to QA. We raised a OSS, for which SAP has replied saying that there was some inconsistencies with the infosource and they have repaired the same in debugging mode. The root-cause for the issue is unknown. So they have not given any notes to us.
But meanwhile we created a new data source and transported it. that worked fine.
Regards,
PM

NO PSA for InfoSource and source system 120 : Maintaing Transfer Rules

Hello BI Experts ,
I am working on Generic data source extraction.
Earlier I mapped all fields infoobjects in Transfer Rules and then loaded data to ODS properly.
But later on I made few changes in Generic data source view and exits in the R3 and replicated the data source to BI.
Then Remapped the fields to infoobjects in Transfer Rules.
Now I can see Transfer Rules Green and all fields are mapped properly.
But when I activated Transfer Rules I am getting message that ,
"There is no PSA for InfoSource ZPS_DATA_BB and source system 120 "
Data source is active in R3.
Communication Structure and Infosource are Active in BI.
Regards ,
Amol K.

hello Surendra ,
I did the same thing already.
I was looking for some otherway.
Thanks for reply.
Regards ,
Amol K.

TC related for IDOC (Defining Port,Defining Partner Profiles...etc) RFC and

Hi All
Can anyone pls give me all the TC related for IDOC (Defining Port,Defining Partner Profiles...etc) RFC and BAPI
Thanks
ss

Hi SS..
 SM59-For creating the RFC destination
 we21- For ports
 we20-Partner profiles.
For more inforamtion Please look at the below information:
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP XI towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
 Thanks and Regards,
 Chandu.
Message was edited by:
 Chandu
null

How can we transport the partner profiles and Port configurations

Hi everybody,
How can we transport the partner profiles and Port configurations. While creating these , system will not ask for Dev class and we cant assign any Transport request number. Then How can we transport these settings?
Your replies are really apreciable.
Thanks and Regards,
Vijay.

Hi,
please have a look of the OSS note: 182172
>>
The partner profiles are stored in the following tables:
Table EDPP1: General partner profile
Table EDP12: Partner profile outbound, additional data NAST
Table EDP13: Partner profile outbound
Table EDP21: Partner profile inbound
Table EDIPHONE: Connection to SAP telephony (optional)
You can use R3TR TABU to manually set the tables into a Customizing request (as of Release 46, into a SYST-type request).
<<
Rgd
Frédéric

Partner profiles and ports

How to transport the configuration of partner profiles and ports from Development to Quality systems.

Hi vidya,
Go through this hope u can get the solution.
WE20 Partner Profile
Here we create partner profile for each and every partner from / to which
the messages will be exchanged.There are 6 types of PF generally only
profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
We specify the partner number and partner type and the agent and
the agent type responsible for handling of errors .
For every message send to the partner we have a outbound record and for
evry message coming from the partner we have the inbound record .
We specify the message in the otbound/inbound records ,double
clicking will take us to the detailed screen where the IDOC Type ,Port
and whether the IDCO will be immediatelt processed or collected are
mentioned.
WE21 Port Definition.
There are 6 types of ports but only 2 types File and Transactional RFC
types of ports are important.
We have to specify the RFC Destination before a port can be created.
SM59 RFC Destination
Here we specify the login settings for the destination including
the I.P address or Application Server name and the User name and
password.The information entered here is used to run Remote Function
Calls(RFC ) on the destination server .We can create number of types
of RFC Destinations but 3 types are important .
R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
The name of the RFC destination should be same as that of Logical
System as it helps in creation of automatic partner profiles.
BD64 Distribution Model . Also known as Customer Distribution Model Used to
define all the messages that will be exchanged between remote systems
and the name of thes logical systems. Any filters can also be specified.
The model once created has to be distributed on every system which will
be communicating ,It can be maintained on only One system.
Reward points if helpful.
Thanks
Naveen khan

Export partner profiles and SM59 Entries before system refresh

Hello All,
How to Export partner profiles and SM59 Entries before system refresh in Netweaver
thanks
Shyam

In SDN search with name RFC export ..you will get so many answers ..
Once again please find the below prcoess for RFC export/import during system refresh.
RFC Export --
go to trans dir.. and then create .ctl file as below
#cd /usr/sap/trans/bin
#vi export_rfc_<sid>_<date>.ctl
#Please create the data file as u201Cexport_<SID>_rfc_<Date>.datu201D
Export
Client=<XXX>
file '/usr/sap/trans/data/export_<SID>_rfc_<Date>.datu2019
delete from rfcattrib
select * from rfcattrib
delete from rfcdes
select * from rfcdes
delete from rfcdoc
select * from rfcdoc
delete from rzllitab
select * from rzllitab
delete from ZTCA_USER_LANG
select * from ZTCA_USER_LANG
delete from rfcsysacl
select * from rfcsysacl
delete from rzllitab
select * from rzllitab
#After that excute export command as below.
R3trans u2013w <export_rfc_<targetSID>_date.log> export_rfc_<targetSID>_date.ctl>
(Format is: R3trans u2013w <logfile> <controlfile>)
Export is finished....
Import
Example:
#cd /usr/sap/trans/bin
#vi import_rfc_pta_11042004.ctl
#Please enter the exported RFC data file in the import control as follows:
import
file '/usr/sap/trans/data/export_pta_rfc_11042004.dat'
(Enter the file name, which is created during the export process)
Regards,
Srinivas Chapa.

Partner Profile and its configuration.

Hi all,
I am creating an SD IDoc using EDI and send it between two servers.
I need to know what is a partner profile and why should we create it.
what are the steps to be followed in maintaining a partner profile and its configuration.
Any pointers will be highly apppreciated.
Thanks in advance,
Regards,
Jose
Edited by: Jose Anthony Reddy on Dec 17, 2007 11:23 PM

Hi Jose,
Below is a material you can go through .
Creating an Outbound Partner Profile
Here you must enter the data manually. Alternatively, you can also transfer the default values from Customizing.
If you are not yet on the change screen of your desired partner, choose SAP Menu ® Tools ® IDoc Interface/ALE ® Administration ® Runtime Settings ® Partner Agreement (WE20).
1. Position the mouse on your partner in the required partner type node. Choose in the Outbound Parameter table.
Key Fields
2. You have already determined partner number and partner type in general partner processing. The partner function from the master data defines the addressee, that is, it is used for further classification purposes. If you have selected outbound processing under Message Control (MC), the function must be identical to the corresponding Message Control field. Otherwise, it is optional.
Partner A (customer 1110) wants to order a material from partner B (vendor 1014). Partner B is of the partner type LI (vendor) and must choose the Message Control value VD (vendor) as the partner function because orders must always be processed using Message Control.
3. Specify the business process with the logical message, within which the IDoc type is used. The logical message is described by three parameters: The message type is based on EDIFACT message types: For example, a purchase order is of type ORDERS. You can further divide the message type with the optional fields message code and message function.
4. Configure the test indicator if you want to send the message as a test.
Message, partner and test indicator are the seven key fields of the outbound partner profiles (the client comes in addition to these). Also see the graphic at the end of this section.
Other Fields
5. In the Outbound options tab page, you can determine whether IDocs are forwarded immediately to the receiving system. You should ensure that your entries are compatible with the Message Control priorities, if you have chosen outbound processing under Message Control. A list of recommended combinations is provided in the section Outbound Processing Under MC: Procedure.
6. You have already defined the Recipient port in Port definition.
7. If a port of type TRFC is used, the Queue Processing field is visible. You can use the indicator to specify whether IDocs are to be sent with qRFC. This sending technique is only possible for recipient SAP systems as of SAP Web AS 6.20.
You should only set this flag if it is really necessary that the IDocs sent are received in the receiving system in the same sequence as they were sent by the sender system. Queuing can cause posting delays in the receiving system, because an IDoc in the queue cannot be posted. In this case, the following IDocs in the queue cannot be posted until the error is resolved.
8. If you have set the Queue Processing indicator, the Rule Name field, which you must then also maintain, appears as well. The rule name defines the rules for queue names. You can specify these rules in the transaction qRFC IDoc Queue Name Rules (WE85).
9. Specify the IDoc type as the Basic type with or without extension. If you want to use a view of your IDoc type (for example, to improve the performance), specify this here.
The figure below shows the m-to-n relationship between logical messages (business meaning) and IDoc types (technical format). Message 1, for example, is always assigned to one IDoc type, while message 3 is assigned to two IDoc types. IDoc type 2, in turn, is also assigned to 2 logical messages.
10. The segment release specifies the release from which the segment definitions (not the IDoc type definition) originates. We recommend that you leave this field blank so that the most recent segment definition is used.
11. You can propose an EDI standard, version and EDI message type for the receiving system in the tab page EDI Standard. Most subsystems, however, should be able to determine these EDI settings themselves (from the logical message).
12. You can define permitted agents for cases in which exceptions occur. This entry overrides the entry in the general partner profiles. Depending on the message, therefore, the exception can be handled by different agents of the same partner.
13. You can specify whether syntax errors are to be ignored or are to lead to a processing error (Cancel Processing flag under syntax check in the tab page outbound options). For more information about exception handling and permitted agents, refer to the following section: Exception Handling
14. If your hardware supports it, create partner and message specific telephony data for outbound IDocs. For more information, see General Partner Profile.
Graphic: Outbound partner profile fields (general)
Key fields are shown in gray. The values for partner, message and test indicator (and client) therefore provide a unique ID for the IDoc type in outbound processing.
Regards,
Praveen

What is the difference between generate partner profile and creat partner

What is the difference between generate partner profile and creat partner profile ?

Create Partner ProfilesAlthough partner profiles are usually created automatically, because of the unusual inbound and outbound profiles needed on the same system, the manual generation of certain profiles is required.
The following subsections describe the partner profile settings for the standard client (assumed here to be ALExxxCyyy), as well as for the corresponding dummy client (assumed to be DUMxxxCyyy). The dummy client partner profiles should have been generated by the automatic generation process completed previously. Nevertheless, these should be checked to ensure that all profiles exist.
Generation of Partner Profiles
The following messages should be added to the 4xx-ORDR model for ALExxxCyyy to DUMxxxCyyy on the reference client:
ORDERS
ORDCHG
ZINVRV
ORDRSP
INVOIC
FIDCMT
The partner profiles should first be generated using the standard auto-generation procedure on the reference client (for SYNCH messages to be created).
This model should now be distributed to the both ALExxxCyyy and DUMxxxCyyy.
The partner profiles should now be generated on the client being configured (i.e. yyy) using the auto-generation procedure defined in the standard ALE configuration procedures.
Generate partner profiles for sending system. (Can only do this if at least 1 message type exists against the sending system's LS). This automatically generates the port if the LS and RFC name are the same.
generate partner profiles tcode BD82
creating partner profiles tcode WE20
 There are two methods for maintaining the partner profile:
 Maintain partner profile manually:
To navigate to the partner profile in the sender system, choose Partner profile -> Partner type of Logical System and click on the required Target system. Under Outbound parameters, choose the Create outbound parameters icon, and enter the values for the outbound parameters according to the slide Sender: Partner Profile (outbound).
To navigate to the partner profile in the sender system, choose Partner profile -> Partner type of Logical System and click on the required Sending system. Under Inbound parameters, choose the Create inbound parameters icon and enter the values for the inbound parameters according to the slide Sender: Partner Profile (inbound).
 Generate partner profile:
Prerequisite: The current distribution model is distributed to all participating systems.
In the sender system, choose: Generate Partner Profile, then check the result in the partner profile (outbound)
In the sender system, choose: Generate Partner Profile, then check the result in the partner profile (inbound)
Regards
Vasu

Configuration Wizard-NW:BI-AS ABAP(Connectivity of BI and Source System): M

Hi friends,
I´m configuring the (NW: BI - AS ABAP (Connectivity of BI and Source System): Maintain) in NWA using Configuration Wizard.
But there is the error in step (NW: BI - AS ABAP (Connectivity of BI and Source System): Maintain > Scenario UI: NW_BI_ABAP_DEFAULT > Scenario Process: Abap Server Integration to BI > Configuration Process > Configuration Unit: Initialize > Config Unit BI System: Initialize > Customizing: Assign Logical System to Client > Write Customizing data to Table T000)
Below error log:
*Write Customizing data to Table T000*
Description:
Exception in step "WriteProfile_1223390220410"
Exception details : com.sap.tc.lm.ctc.metamodel.exception.ActionExecuteException: Exception during the import of the profile!
State
Step finished with error
Support Information
Type of Action
WriteProfile
Debug Events
WriteProfile:Write Customizing data to Table T000
Library: sap.com/tclmconfig~bs
SourcePath ./com_sap_nw_bi_abap_default_maintain/ext_12064772269223/ext_1206447991146/Process_1207123636083/proc_1196064316796/Process_1204300420808/proc_1204300371034/WriteProfile_1223390220410
Time 2011/11/03 at 15:36:57
Schema content/NetWeaver/Common/Customizing/Clients/T000.xsd
Type : View Maintenance
Input
<TABLE_T000 xmlns:expr="http:/sap.com/ctc/expressions"><T000><MANDT>100</MANDT><LOGSYS>SOLCLNT100</LOGSYS></T000></TABLE_T000>
Schema
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:vma="http://www.sap.com/ctc/vma"
elementFormDefault="qualified"> <xsd:element name="TABLE_T000" type="TABLE_T000"></xsd:element> <xsd:complexType name="TABLE_T000"> <xsd:sequence> <xsd:element name="T000" type="T000"> <xsd:annotation> <xsd:appinfo
source="http://www.sap.com/ctc"> <vma:vmacontext table="T000" isupdate="false"/> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:complexType> <xsd:complexType name="T000"> <xsd:sequence> <xsd:element name="MANDT" type="xsd:string"> <xsd:annotation> <xsd:appinfo source="http://www.sap.com/ctc"> <vma:vmaproperty column="MANDT"/> </xsd:appinfo>
</xsd:annotation> </xsd:element> <xsd:element name="LOGSYS" type="xsd:string"> <xsd:annotation> <xsd:appinfo source="http://www.sap.com/ctc"> <vma:vmaproperty column="LOGSYS"></vma:vmaproperty> </xsd:appinfo> </xsd:annotation> </xsd:element
</xsd:sequence> </xsd:complexType> </xsd:schema>
Destination parameters
user : SOLMAN_ADMIN
password : % secure content %
host : cdsolman
sysnr : 01
client : 100
language : en
Stack Trace
Caused by: com.sap.tc.lm.ctc.cul.api.CULServiceException: Exception during the import of the profile!
 at com.sap.tc.lm.ctc.cul.serviceimpl.writeProfile.CULServiceWriteProfileImpl.writeProfile(CULServiceWriteProfileImpl.java:98)
 at com.sap.tc.lm.ctc.cul.serviceimpl.process.WriteProfileControllerImpl.execute(WriteProfileControllerImpl.java:160)
 ... 16 more
Caused by: com.sap.tc.lm.ctc.cul.cpi.context.ConfigurationBrokerException: <Localization failed: ResourceBundle='com.sap.tc.lm.ctc.cul.cpi.CPIResourceBundle', ID='xml_parsing_exception', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key xml_parsing_exception
 at com.sap.tc.lm.ctc.cul.broker.BrokerWriteProfileImpl.writeProfile(BrokerWriteProfileImpl.java:79)
 at com.sap.tc.lm.ctc.cul.serviceimpl.writeProfile.CULServiceWriteProfileImpl.writeProfile(CULServiceWriteProfileImpl.java:95)
 ... 17 more
Caused by: com.sap.tc.lm.ctc.provider.vmaprovider.exceptions.VMAProviderBaseException: Incorrect XML
 at com.sap.tc.lm.ctc.provider.vmaprovider.util.VMAUtil.getDocument(VMAUtil.java:349)
 at com.sap.tc.lm.ctc.provider.vmaprovider.util.VMAUtil.setXmlValue(VMAUtil.java:250)
 at com.sap.tc.lm.ctc.provider.vmaprovider.util.JCOProfileExecutorImpl.executeContext(JCOProfileExecutorImpl.java:310)
 at com.sap.tc.lm.ctc.provider.vmaprovider.util.JCOProfileExecutorImpl.executeChildNode(JCOProfileExecutorImpl.java:183)
 at com.sap.tc.lm.ctc.provider.vmaprovider.util.JCOProfileExecutorImpl.executeProfile(JCOProfileExecutorImpl.java:129)
 at com.sap.tc.lm.ctc.provider.vmaprovider.VMAWriteProfile.writeProfile(VMAWriteProfile.java:59)
 at com.sap.tc.lm.ctc.cul.broker.BrokerWriteProfileImpl.writeProfile(BrokerWriteProfileImpl.java:144)
 at com.sap.tc.lm.ctc.cul.broker.BrokerWriteProfileImpl.writeProfile(BrokerWriteProfileImpl.java:73)
Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Incorrect encoded sequence detected at character (hex) 0x6f, (bin) 1101111. Check whether the input parsed contains correctly encoded characters. Encoding used is: 'utf-8'(:main:, row:1, col:637)(:main:, row=1, col=637) -> com.sap.engine.lib.xml.parser.ParserException: Incorrect encoded sequence detected at character (hex) 0x6f, (bin) 1101111. Check whether the input parsed contains correctly encoded characters. Encoding used is: 'utf-8'(:main:, row:1, col:637)
 at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:139)
 at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
 at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:76)
 at com.sap.tc.lm.ctc.provider.vmaprovider.util.VMAUtil.getDocument(VMAUtil.java:341)
Caused by: com.sap.engine.lib.xml.parser.ParserException: Incorrect encoded sequence detected at character (hex) 0x6f, (bin) 1101111. Check whether the input parsed contains correctly encoded characters. Encoding used is: 'utf-8'(:main:, row:1, col:637)
 at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:209)
 at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:207)
 at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143)
All the others steps were finished successfully
Only this step is with error. I don´t know that to do.
Regards,
Ricardo Arriado
Edited by: Ricardo Arriado on Nov 4, 2011 6:24 PM

Hi,
Please double check the JCO user and the authorization.
Or
Apply these two notes, it should resolve ur issue
1493124 CTC: Check table existence before table whitelist
1471762 CTC: Automated Configuration:
Hope this helps u.
Best Regards
Vijay K

Background job is running for long tome in source system (ECC)

Hi All,
Background job is running for long tome in source system (ECC) while extracting data to PSA.
I checked in ECC system SM66,SM50 the job is still running
in SM37 the job is Active
There are only maximum 7000 records the extractor is 2LIS_02_ITM but it is taking 11 to 13 hours to load to PSA daily
I had checked enhancements every thing is correct.
Please help me on this how can I solve this issue.
Regards
Supraja K

Hi sudhi,
The difference between Call customer enhancement... and Result of customer enhancement:... is very less we can say this as a second.
The difference is between LUWs confirmed and 1 LUWs -
   and Call customer enhancement -
Please find the job log details below, and give me the solution to ressolve this
01:06:43 ***01:06:43 * ztta/roll_extension........... 2000000000                              *                 R8           050
                 R8           048
01:06:43 1 LUWs confirmed and 1 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DATA     RSQU          036
06:56:31 Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 5.208 records                  R3           407
06:56:31 Result of customer enhancement: 5.208 records                                              R3           408
06:56:31 Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 5.208 records                      R3           407
06:56:31 Result of customer enhancement: 5.208 records                                              R3           408
06:56:31 PSA=1 USING SMQS SCHEDULER / IF [tRFC=ON] STARTING qRFC ELSE STARTING SAPI                 R3           299
06:56:31 Synchronous send of data package 1 (0 parallel tasks)                                      R3           410
06:56:32 tRFC: Data Package = 0, TID = , Duration = 00:00:00, ARFCSTATE =                           R3           038
06:56:32 tRFC: Start = 00.00.0000 00:00:00, End = 00.00.0000 00:00:00                               R3           039
06:56:32 Synchronized transmission of info IDoc 3 (0 parallel tasks)                                R3           414
06:56:32 IDOC: Info IDoc 3, IDoc No. 1549822, Duration 00:00:00                                     R3           088
06:56:32 IDoc: Start = 04.10.2011 06:56:32, End = 04.10.2011 06:56:32                               R3           089
06:56:32 Altogether, 0 records were filtered out through selection conditions                      RSQU          037
06:56:32 Synchronized transmission of info IDoc 4 (0 parallel tasks)                                R3           414
06:56:32 IDOC: Info IDoc 4, IDoc No. 1549823, Duration 00:00:00                                     R3           088
06:56:32 IDoc: Start = 04.10.2011 06:56:32, End = 04.10.2011 06:56:32                               R3           089
06:56:32 Job finished                                                                               00           517
Regards
Supraja

Standard report which gives Record count of ODS, Cube and Source system.

Hi-
Is there any standard report which gives the record count of ODS, Cube and Source system?
or
If any one has ABAP program which takes care of record count pls let me know.
Thanks in advance

I don't understand. You need to check the data loads. What for do you want a list of ODS, Cubes and sources systems?
You can use messages from process chains to monitor the data loads.
You can also use an abap program inside teh process chains to save data into a table and then an abap report to see if everything went OK.
But, thinking again, you may be able to use BW statistics to get some of the information you need. Check the help for BW statistics, it might give you an idea of what you can do.
Regards,
Diego

Where ca u assign Partner profile in XI system

Hi
in File to IDOC scenario
Where ca u assign Partner profile in XI system
bye..

Hi
No need to create partner profile in XI.
these r done in R/3
Check this link for IDOC
Configure IDOC
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
Reagrds
Sachin

Regenerating ports for Partner Profiles and Source System (RSA1)

Similar Messages

Maybe you are looking for