IDoc structure mismatch between SAP R/3 and PI

Hi,
There is an interface in PI which receives IDoc from SAP R/3 system. I have been facing an issue of IDoc structure mismatch (in terms of data present in it) between SAP R/3 and when PI receives the IDoc.
To be more precise,
In SAP R/3 system, the value ABC is present in the field DOCNUM in the IDoc.
But when the PI receives the same IDoc from SAP R/3 (as seen in Integration Engine), the value ABC is present in a different field and the DOCNUM field is empty.
<DOCNUM></DOCNUM>
<ARCKEY>ABC</ARCKEY>
The first step towards resolution was to delete and reimport the IDoc metadata from SAP R/3 in PI system using IDX2, which did not help in this case.
Could anyone please help in resolving the field mismatch between the IDoc triggered from SAP R/3 and the IDoc received by PI.
Regards,
Prajeet

Hi Prajeet,
it's long ago but your question has not been finally solved, so let me try to give you an answer. We are facing the same problem after patching our PI.
I think the reason for the different behaviour is related to SAP note 1233908, where SAP has changed the IDoc adapter.
https://service.sap.com/sap/support/notes/1233908
Regards,
Lars

Similar Messages

Connectivity between SAP ECC system and SAP BI

Connectivity between SAP ECC system and SAP BI
Hi BI-experts!
I would like to load e.g. transaction data from SAP ECC system into SAP BI system.
The Loading process is hanging in processing step u201CSERVICE APIu201D.
The process in hanging in status "yellow" and then changed after a while to status u201Credu201D.
[0FI_AR_4 |http://www.file-upload.net/view-1447743/0FI_AR_4.jpg.html ]
The following steps within Load process are yellow and then red:
Extraction (messages): Missing messages
Missing message: Request received
Missing message: Number of sent records
Missing message: Selection completed
Transfer (IDocs and TRFC): Missing messages or warnings
Request IDoc : Application document posted (is green)
Data Package 1 : arrived in BW ; Processing : 2nd processing step not yet finished
Info IDoc 1 : sent, not arrived ; Data passed to port OK
Info IDoc 2 : sent, not arrived ; Data passed to port OK
Info IDoc 3 : sent, not arrived ; Data passed to port OK
Info IDoc 4 : sent, not arrived ; Data passed to port OK
Subseq. processing (messages) : Missing messages
Missing message: Subseq. processing completed
DataStore Activation (Change Log) : not yet activated
Question:
Can some one tell me whether my distribution model or other settings are wrong?
I created 2 distribution model (BD64), one from SAP BW system and other from SAP BI system with message types RSRQST, RSINFO, RSSEND
Thank you very much!

Hi Holger.
this issue is related to the RFC but not the one which is communicating from BI to R/3 rather the one which is communicating from R/3 to BI follow these steps.
1. check your BI system logical name from the myself source system.
2. go the ECC and run the transaction sm59
3. go the ABAP Connection folder and search for your RFC which name would be by default as per your BI logical system name.
4. double click it and edit it now check whether the Target hostname or ip is OK.
5. In the logon tab check the client number User and password settings.
Save it and test it with both Connection Test and Remote Logon.
if every thing work fine i hope your problem will be solved.
kind regards,
Zeeshan

How we can import an IDOC structure from one SAP system to another w/o ALE

Hi Gurus,
How we can import an IDOC structure from one SAP system to another? we're not able to use ALE tech, these two sap systems are isolated.
Any response will be awarded!
Thanks a lot.
Samson

hi,
1.One is by change pointer concept i.e by executing the RBDMIDOC.We can generate the idoc and automatically to the inbound System.
2.By executable program also like bd10 and bd11.
Regards,
SHIVA(reward if helpful).

How we can import an IDOC structure from one SAP system to another

Hi Gurus,
How we can import an IDOC structure from one SAP system to another? If we're using ALE, how can we do that? Please can someone give me the process and necessary t codes.
Any response will be awarded!
Thanks a lot.
Samson

hi!
Define the logical system names in both the systems.
Logical system names :SAP001
SAP002
SAP001 FOR 001 CLIENT
SAP002 FOR 002 CLIENT
These two logical system definitions should be present in both the systems.
Assign the logical systems to the client. (in both the systems)
Assign SAP001 to 001 CLIENT
Assign SAP002 to 002 CLIENT
you can See these in transaction SALE.
After this define the rfc DESTINATION IN sm59. (in both the systems)
In 001 client create the RFC destination name SAP002
In the tab log on security, give the user name and password and client of the 002 client and save it.
Similarly do the reverse in the 002 Client.
In 001 client create the port.(Transaction WE21)
Specify the RFC destination name as SAP002.
Now you can define the ports, (both the systems)
Create the partner profile for partner(ie gve logical system name of partner) , so give as SAP002.
partner profile in both the systems.
Now create the distribution model in BD64 and goto edit>model view>distribute.
The same model view will be visible n distributed to the partner system also..which in this case is sap002.
U may trigger the idoc from we19 and chk its status in we05.
Please let me know if you need further info on this.

Verify the data between SAP R/3 and SAP BW

Hi Experts,
How to verify the data between SAP R/3 and SAP BW at the time of data mismatches in reports.
give me the proper solution.
Thanks,
Syam

Hello,
You must know what is the infoprovider source of the data shown in the report.
Once you know it, check the content filtering by same restrictions as in the mismatch report. Now you have the data in BW.
Then you have to know the proper transation or table in R/3, from where the extractor retrieves the data to populate the infoprovider; make same restrictions and compare it with data in BW.
Regards

Difference between SAP 4.7 and ECC 5.0

hi frnds
.what is the difference between SAP 4.7 and ECC 5.0?
regards

Hi,
Following are the basic differences as far as MM Module is concerned
Pickup list - Batch where-used list display in transaction MB56
u2022 Until release 4.7, the top-down and bottom-up analyses in the function pickup list for batch where-used list (transaction MB5C) were displayed only in the form of simple output lists. As of release 6.00 of SAP ERP Central Component, the function pickup list for batch where-used list branches to the batch where-used list itself (transaction MB56).
u2022 In addition, user can define how the data in the batch where-used list is displayed, in the initial screen.
u2022 User can use all the settings available in the batch where-used list. For example, he can expand transfer posting or display vendor batch. However, it is not possible to limit the selection to valid plants in the initial screen of the pickup list.
Usability enhancements for transaction MIGO for the posting of goods movements
u2022 For goods movements that refer to purchase orders as reference documents (for example, goods receipt, goods issue, subsequent adjustment), user can specify the ordering plant as an additional selection criterion directly next to the purchase order number and the item number.
u2022 There is a new default value: "copy account assignment fields." When entering other goods receipts, user can copy existing account assignment data from the previous item to use as the default values for a new item. To do this, user has to set the copy account assignment fields indicator in the default values.
u2022 User changes the default values in the menu path "Settings -> Default Values."
u2022 Goods movement is monitored with reference to a material document. When you enter the following goods movements, it is possible to specify a material document, such as the following, as the reference document:
Goods receipt
Goods issue
Transfer posting
Remove from storage
u2022 Note that these material documents must be documents that have arisen from a goods movement without reference ("Others") and that are not reversal documents.
New report : display list of invoice documents (MIR5)
u2022 Logistics invoice verification offers a new report display list of invoice documents (RMMR1MDI), w hich user can use to display such a list (Transaction is MIR5).
u2022 As an addition to the existing program invoice overview (transaction code MIR6), user have extended selection criteria and display options. For example, on the initial screen user can make selections by one-time customers, invoice gross amount, and entry date.
u2022 User can also show an expert mode, which enables him to select at plant level by FI document, GL A/c posting, and Material Posting.
u2022 In the output list, the report shows both posted and held invoices.
u2022 It does not show invoices without a corresponding FI document; such as invoices planned for verification in the background or which the software has already verified as containing errors.
Requirement prioritizations in materials management
u2022 With Requirement Prioritization functionality user can assign requirement urgency at item level in purchasing and reservation documents.
u2022 The software determines the relevant requirement priority (overall priority) of a material requisition from the combination of requirement urgency group and organizational priority.
Mass maintenance of outline agreements
The following two transactions available:
u2022 Mass maintenance for contracts: transaction code MEMASSCONTRACT
u2022 Mass maintenance for scheduling agreements: transaction code MEMASSSA
Commitment plan for purchase contracts
u2022 With the function of the commitment plan for purchase contracts, it is possible to pre plan value consumption for a purchase contract.
u2022 To this end, a commitment plan is generated for each document item of the relevant contract.
u2022 This commitment plan itself can have any number of items.
u2022 User can define a value and a validity date for each commitment plan item.
u2022 This enables user to pre plan different values for different periods of time.
u2022 The software generates an earmarked fund document for a defined commitment plan item.
u2022 This earmarked funds document can in turn contain several different items with different account assignments.
u2022 The software adopts these account assignments from the item account assignments of the commitment plan.
u2022 If a purchase requisition or purchase order references this contract, the earmarked funds document is copied into the purchase order, and the account assignment is adopted from that document.
u2022 Account assignment to a different account assignment object is then no longer allowed.
Availability check in "Enjoy purchase order and requisition"
u2022 Display and checking of availability are invokable separately in the "Enjoy purchase order and requisition" function, in line with the software behavior on the sales side.
u2022 User invoke the display and checking of availability in the "Enjoy purchase order" function (transaction code ME21N) and the "Enjoy purchase requisition" function (transaction code ME51N) as follows:
To display the availability overview, choose the menu path "Environment -> Availability." - To check availability, choose the "Check Availability" icon.
Until this release, if user carried out the availability check for an item of a stock transport order, the software adopted confirmations as per the desired date/time only.
u2022 Two settings are possible with availability check:
Confirmation as per desired date/time (this is the standard setting and corresponds to previous software behavior)
Delivery proposal - Full confirmation
External services: putting service items in the purchase order on hold (changed)
User can put purchase orders with service items on hold if these items do not contain any errors. Purchase orders with service items can also be put on hold if errors occur only at header level or as a result of the availability check.
Customizing transactions OX18 replaced by view
The assigned customizing transactions have been replaced by the following view in the following implementation guide activity in customizing for the enterprise structure: Assign plant to company code: transaction OX18 replaced by view V_T001K_Assign. One will find this activity in the implementation guide under the menu path "Enterprise Structure -> Assignment -> Logistics General -> Assign Plant to Company Code."
Goods receipt: new movement types in inventory management
The following new movement types are available in inventory management:
107: Goods receipt to valuated goods receipt blocked stock
109: Goods receipt from valuated goods receipt blocked stock
Prepayment of invoices
This functionality is characterized as follows:
u2022 User can trigger prepayment of vendor invoices in logistics invoice verification.
u2022 User use the prepayment function for vendors with whom organisation has a good, long-standing relationship.
u2022 The function enables payment soon after issue of the invoice and full exploitation of the date of required payment and existing cash discounts, by posting the vendor liabilities, taxes, and cash discounts in financial accounting in advance.
u2022 The software executes the payment of the invoice regardless of the relevant goods receipt and the outcome of the invoice verification check.
u2022 Most logistics invoice verification standard functions are not affected by the prepayment function.
u2022 When the software posts invoices, it continues to execute the standard checks.
u2022 If the software has already posted the prepayment document, user can make only restricted changes to the header fields of the invoice.
u2022 To ensure adequate and orderly financial accounting postings, a prepayment clearing account has been added to SAP ERP Central Component.
u2022 Upon prepayment, the software debits this account and then settles the account again after executing the check.
Purchasing accounting information to the former SAP Business Information Warehouse
u2022 With the transfer of the purchasing account information to the former SAP Business Information Warehouse component (whose functionality is now part of SAP Net Weaver), it is now possible to maintain Info Cubes, reports, and queries that can determine how and where the costs from purchasing documents have been assigned and controlled.
u2022 As part of the software, a new data source (2LIS_02_ACC) has been created and the purchasing extraction process extended to cover the account information for purchasing orders, schedule agreements, and contracts.
Automatic settlement of planned delivery costs with evaluated receipt settlement (MRDC)
u2022 A new report (RMMR1MDC), available within the logistics invoice verification, can be used to automatically settle planned delivery costs.
u2022 To invoke the report, from the SAP easy access screen, choose the menu path "Logistics -> Materials Management -> Logistics Invoice Verification -> Automatic Settlement -> Automatic Delivery Cost Settlement" (transaction code MRDC).
u2022 Functionality for report RMMR1MRS is enhanced.
u2022 User can use the report RMMR1MRS, "Evaluated receipt settlement with logistics invoice verification (LIV)" (transaction code MRRL), to settle planned delivery costs in addition to goods and service items within logistics invoice verification.
u2022 To do so, set the relevant indicator on the initial screen of the report.
Parking service items
It is now possible to put service orders without errors or with commitment errors on hold.
Report MB5B : Stock on Posting Date
u2022 This Report is available with u201CNon-Hierarchyu201D display option which provides details of Opening, Receipt, Issue and Closing balances of Stock with quantity and value both for a given period.
u2022 This functionality is not available in Release 4.7.
Stock Transfer Between Storage Locations
u2022 Function of stock transport orders between storage locations is available from ECC 6.0 onwards.
u2022 As a result of which user can input issuing storage location with supplying plant.
u2022 Facility of using different delivery types for different issuing storage locations is available.
u2022 Shipping Point data can also be determined based on the issuing storage location
Regards
Priyanka.P
AWARD IF HELPFULL

Functional Transaction Difference between SAP 4.7 and ECC 6.0 in Case of SD

Hi,
Experts can you Pls tell Transaction difference between SAP 4.7 and ECC 6.0 in case of SD module.
Like VA05n is one transactional difference.
regards,
Rohan

Refer below for the Transaction codes, You can find the functional differences in Release note or Solution browser > Apart from the functional Delta most of the reports are in ALV Grid disply and few changes you can note in Organizational Structure Assignment and consistency check , Document flow , Purchase Order Data tab and Item Conditions so on
VA05N List of Sales Orders
VA25N Quotation List
VF05N Billing Document List
VA45N List of Contracts
OVX8N Check Report Organization Sales
OVX3N Assign sales organization to company code
OVXKN Assign distribution channel to sales organization
OVXAN Assign division to sales organization
OVXGN Set up sales area
OVXMN Assign sales office to sales area
OVXJN Assign sales group to sales office
OVX6N Assign sales organization - distribution channel - plant

Delta functionality between SAP 4.7 and ECC 6

Hi All,
Can anyone please provide me with any documents or links on delta functionality between SAP 4.7 and ECC 6.0 in MM/WM.
Any information would be helpful.
Regards
Prashant

Hello
Following are the basic differences as far as MM Module is concerned;
Pickup list - Batch where-used list display in transaction MB56
u2022 Until release 4.7, the top-down and bottom-up analyses in the function pickup list for batch where-used list (transaction MB5C) were displayed only in the form of simple output lists. As of release 6.00 of SAP ERP Central Component, the function pickup list for batch where-used list branches to the batch where-used list itself (transaction MB56).
u2022 In addition, user can define how the data in the batch where-used list is displayed, in the initial screen.
u2022 User can use all the settings available in the batch where-used list. For example, he can expand transfer posting or display vendor batch. However, it is not possible to limit the selection to valid plants in the initial screen of the pickup list.
Usability enhancements for transaction MIGO for the posting of goods movements
u2022 For goods movements that refer to purchase orders as reference documents (for example, goods receipt, goods issue, subsequent adjustment), user can specify the ordering plant as an additional selection criterion directly next to the purchase order number and the item number.
u2022 There is a new default value: "copy account assignment fields." When entering other goods receipts, user can copy existing account assignment data from the previous item to use as the default values for a new item. To do this, user has to set the copy account assignment fields indicator in the default values.
u2022 User changes the default values in the menu path "Settings -> Default Values."
u2022 Goods movement is monitored with reference to a material document. When you enter the following goods movements, it is possible to specify a material document, such as the following, as the reference document:
Goods receipt
Goods issue
Transfer posting
Remove from storage
u2022 Note that these material documents must be documents that have arisen from a goods movement without reference ("Others") and that are not reversal documents.
New report : display list of invoice documents (MIR5)
u2022 Logistics invoice verification offers a new report display list of invoice documents (RMMR1MDI), w hich user can use to display such a list (Transaction is MIR5).
u2022 As an addition to the existing program invoice overview (transaction code MIR6), user have extended selection criteria and display options. For example, on the initial screen user can make selections by one-time customers, invoice gross amount, and entry date.
u2022 User can also show an expert mode, which enables him to select at plant level by FI document, GL A/c posting, and Material Posting.
u2022 In the output list, the report shows both posted and held invoices.
u2022 It does not show invoices without a corresponding FI document; such as invoices planned for verification in the background or which the software has already verified as containing errors.
Requirement prioritizations in materials management
u2022 With Requirement Prioritization functionality user can assign requirement urgency at item level in purchasing and reservation documents.
u2022 The software determines the relevant requirement priority (overall priority) of a material requisition from the combination of requirement urgency group and organizational priority.
Mass maintenance of outline agreements
The following two transactions available:
u2022 Mass maintenance for contracts: transaction code MEMASSCONTRACT
u2022 Mass maintenance for scheduling agreements: transaction code MEMASSSA
Commitment plan for purchase contracts
u2022 With the function of the commitment plan for purchase contracts, it is possible to pre plan value consumption for a purchase contract.
u2022 To this end, a commitment plan is generated for each document item of the relevant contract.
u2022 This commitment plan itself can have any number of items.
u2022 User can define a value and a validity date for each commitment plan item.
u2022 This enables user to pre plan different values for different periods of time.
u2022 The software generates an earmarked fund document for a defined commitment plan item.
u2022 This earmarked funds document can in turn contain several different items with different account assignments.
u2022 The software adopts these account assignments from the item account assignments of the commitment plan.
u2022 If a purchase requisition or purchase order references this contract, the earmarked funds document is copied into the purchase order, and the account assignment is adopted from that document.
u2022 Account assignment to a different account assignment object is then no longer allowed.
Availability check in "Enjoy purchase order and requisition"
u2022 Display and checking of availability are invokable separately in the "Enjoy purchase order and requisition" function, in line with the software behavior on the sales side.
u2022 User invoke the display and checking of availability in the "Enjoy purchase order" function (transaction code ME21N) and the "Enjoy purchase requisition" function (transaction code ME51N) as follows:
To display the availability overview, choose the menu path "Environment -> Availability." - To check availability, choose the "Check Availability" icon.
Until this release, if user carried out the availability check for an item of a stock transport order, the software adopted confirmations as per the desired date/time only.
u2022 Two settings are possible with availability check:
Confirmation as per desired date/time (this is the standard setting and corresponds to previous software behavior)
Delivery proposal - Full confirmation
External services: putting service items in the purchase order on hold (changed)
User can put purchase orders with service items on hold if these items do not contain any errors. Purchase orders with service items can also be put on hold if errors occur only at header level or as a result of the availability check.
Customizing transactions OX18 replaced by view
The assigned customizing transactions have been replaced by the following view in the following implementation guide activity in customizing for the enterprise structure: Assign plant to company code: transaction OX18 replaced by view V_T001K_Assign. One will find this activity in the implementation guide under the menu path "Enterprise Structure -> Assignment -> Logistics General -> Assign Plant to Company Code."
Goods receipt: new movement types in inventory management
The following new movement types are available in inventory management:
107: Goods receipt to valuated goods receipt blocked stock
109: Goods receipt from valuated goods receipt blocked stock
Prepayment of invoices
This functionality is characterized as follows:
u2022 User can trigger prepayment of vendor invoices in logistics invoice verification.
u2022 User use the prepayment function for vendors with whom organisation has a good, long-standing relationship.
u2022 The function enables payment soon after issue of the invoice and full exploitation of the date of required payment and existing cash discounts, by posting the vendor liabilities, taxes, and cash discounts in financial accounting in advance.
u2022 The software executes the payment of the invoice regardless of the relevant goods receipt and the outcome of the invoice verification check.
u2022 Most logistics invoice verification standard functions are not affected by the prepayment function.
u2022 When the software posts invoices, it continues to execute the standard checks.
u2022 If the software has already posted the prepayment document, user can make only restricted changes to the header fields of the invoice.
u2022 To ensure adequate and orderly financial accounting postings, a prepayment clearing account has been added to SAP ERP Central Component.
u2022 Upon prepayment, the software debits this account and then settles the account again after executing the check.
Purchasing accounting information to the former SAP Business Information Warehouse
u2022 With the transfer of the purchasing account information to the former SAP Business Information Warehouse component (whose functionality is now part of SAP Net Weaver), it is now possible to maintain Info Cubes, reports, and queries that can determine how and where the costs from purchasing documents have been assigned and controlled.
u2022 As part of the software, a new data source (2LIS_02_ACC) has been created and the purchasing extraction process extended to cover the account information for purchasing orders, schedule agreements, and contracts.
Automatic settlement of planned delivery costs with evaluated receipt settlement (MRDC)
u2022 A new report (RMMR1MDC), available within the logistics invoice verification, can be used to automatically settle planned delivery costs.
u2022 To invoke the report, from the SAP easy access screen, choose the menu path "Logistics -> Materials Management -> Logistics Invoice Verification -> Automatic Settlement -> Automatic Delivery Cost Settlement" (transaction code MRDC).
u2022 Functionality for report RMMR1MRS is enhanced.
u2022 User can use the report RMMR1MRS, "Evaluated receipt settlement with logistics invoice verification (LIV)" (transaction code MRRL), to settle planned delivery costs in addition to goods and service items within logistics invoice verification.
u2022 To do so, set the relevant indicator on the initial screen of the report.
Parking service items
It is now possible to put service orders without errors or with commitment errors on hold.
Report MB5B : Stock on Posting Date
u2022 This Report is available with "Non-Hierarchy" display option which provides details of Opening, Receipt, Issue and Closing balances of Stock with quantity and value both for a given period.
u2022 This functionality is not available in Release 4.7.
Stock Transfer Between Storage Locations
u2022 Function of stock transport orders between storage locations is available from ECC 6.0 onwards.
u2022 As a result of which user can input issuing storage location with supplying plant.
u2022 Facility of using different delivery types for different issuing storage locations is available.
u2022 Shipping Point data can also be determined based on the issuing storage location.
If u want to know more go through the following links
http://solutionbrowser.erp.sap.fmpmedia.com/
http://help.sap.com/saphelperp2005vp/helpdata/en/43/6880cbb88f297ee10000000a422035/frameset.htm_
https://wiki.sdn.sap.com/wiki/display/ERP6/ERP2005+Upgrade
check following
http://help.sap.com/bp_bblibrary/500/html/U40_EN_IN.htm
for more help check following
http://help.sap.com/bp_bblibrary/500/BBlibrary_start.htm
Go through the following link for the Delta functionality notes
http://solutionbrowser.erp.sap.fmpmedia.com/
Regards
Priyanka.P

Connection between SAP R/3 and SAP XI with RFC

Hi Experts,
I am beginner in SAP XI.
We are using SAP XI 3.0 SP 9 and SAP R/3 4.6 C
I am trying to validate a connection between SAP R/3 and SAP XI with RFC.
I followed all the weblogs ,and i did exactly the same way, but I am unsucessful...
Schema not available Exception
com.sap.aii.af.service.cpa.CPAException: Schema not available for RFC|3b787a8035c111d6bbe0efe50a1145a5|http://sap.com/xi/XI/System.
at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataSAXHandler.endElement(DirectoryDataSAXHandler.java:262)
at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler.endElement(SAXDocHandler.java:154)
at com.sap.engine.lib.xml.parser.XMLParser.scanEndTag(XMLParser.java:1826)
at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1722)
at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2298)
at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1719)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2701)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:162)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:126)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:136)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:209)
at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:270)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:331)
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:143)
at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataParser.updateCentralCache(DirectoryDataParser.java:54)
at com.sap.aii.af.service.cpa.impl.cache.CacheManager.updateCacheWithDirectoryData(CacheManager.java:713)
at com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(CacheManager.java:595)
at com.sap.aii.af.service.cpa.impl.cache.CacheManager$CacheUpdateRunnable.run(CacheManager.java:440)
at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)
Please help me out on this
Thanks in advance
Raju

hi,
try refreshing you CAP cache:
741214 (check this note)
and check if the refresh was successful
(CPA history)
Regards,
michal

Secure Communication between SAP R/3 and SAP portal(WAS Java)

Hi All,
We have a requirement where client says ,there needs to be a SSL tunnel established between SAP R/3 and Portal(through ITS) to access R/3 through portal
Do we have to use SSL for that or SNC?I heard SNC is a mechanism which have to be used here since it uses DIAG protocol to connect but not Http.Is it true?Kindly give some more ideas on this.
Other thing is to do this they need to open a port between for using Firewall.Can you guide which SAP port has to be open for this connection?
Thanks In Advance
Regards
Rani A

Hi Rani,
what the ITS Admin is, is explained in the docs to the <a href="http://help.sap.com/saphelp_nw04/helpdata/en/44/28611e0bd26493e10000000a1553f7/frameset.htm">ITS Admin Tool</a>. This also includes how to access it.
Usually specifiying the ABAP backend is done by maintaining the <a href="http://help.sap.com/saphelp_nw04/helpdata/en/44/2b67fe369b060ae10000000a155369/frameset.htm">Global Service File Parameters</a>.
The <a href="http://help.sap.com/saphelp_nw04/helpdata/en/44/2aa8081a3a060ae10000000a155369/frameset.htm">SNC configuration</a> is part of the <a href="http://help.sap.com/saphelp_nw04/helpdata/en/44/2a95a61a3a060ae10000000a155369/frameset.htm">Security Configuration</a> and also done in the ADM instance of the ITS.
Regards,
Patrick

Difference between SAP Business Workflow and CRM Workflow

Hello guys,
Is there any difference between SAP Business Workflow and CRM Workflow?
Are there others workflows types in SAP?
In all SAP Workflow Courses (BIT600, BIT601, BIT603, BIT610) only was talked about SAP Business Workflow, and nothing about CRM Workflow.
Thanks a lot!
Kleber

Hello Kleber,
There is not much of the differance between CRM workflows and SAP Business workflows..
Workflows are esentially part of Basis (BC) components and hence its the same across all SAP products as all these products have components of Basis(BC) in them...
To Conclude, SAP Busines workflows and CRM workflows are the same things... However when you work on CRM, the BOR objects would be belonging to CRM and not to ECC... However conceptwise , there in no change at all.. If you learn BIT100......, you can also work on CRM workflows..
Regards,
Anand

Purchase price difference between SAP R/3 and BWI report

Hi
Purchase price difference between SAP R/3 and BWI report
What is purchase price variance ?, my user is telling that in SAP R/3, purchase price variance 100 and in BWI report it is 200 .
Any other terminologies are there for purchase price variance ?
And any idea wherefrom BWI will take this purchase price variance ?
Thanks In advance

Purchase price variance is he difference in price between the amount paid to the supplier and the planned or standard cost of that item
Request you to check your data first in your Cube/ODS, better would be to check in the data container where the data is first loaded.
Also check if this field is getting directly loaded as 1-to-1 mapping.

Fatal error C1900: Il mismatch between 'P1' version '20080116' and 'P2' version '20070207'

Hi all,
I have a Team Foundation Build Agent that has Visual Studio Team System 2008 Test Edition installed. One of the solutions that I compile with that Build Agent gives me the following errors:
VCBUILD : fatal error C1047: The object or library file '.\bin\Release\main.obj' was created with an older compiler than other objects; rebuild old objects and libraries
LINK : fatal error LNK1257: code generation failed
VCBUILD : fatal error C1900: Il mismatch between 'P1' version '20080116' and 'P2' version '20070207'
LINK : fatal error LNK1257: code generation failed
I've searched online and found that other people have experienced the same problem:
http://software.intel.com/en-us/forums/intel-c-compiler/topic/62516/
http://nuicode.com/issues/266
In the second posting one states "I had the same Error! After installing Service Pack1 for VS2008 it worked!". Thats great for him but I don't see any such update for the Test Edition of Visual Studio Team System 2008 - Test Edition.
What can I do to get rid of that problem?
Thanks!

Hello ACKH
I once handled a similar case in newsgroups. That case exhibit a almost same symptom. Please check out my summary below:
Problem
In that case, the customer has a DLL project that you had built on a machine where VS 2008 SP1 was installed. You then attempted to rebuild that project on a machine without SP1, and got a fatal compiler error C1900 “IL mismatch between ‘P1’ version ‘20080116’ and ‘P2’ version ‘20070207’”, and then LNK1257 “Code generation failed”. He found that rebuilding your static library alleviated the errors, but cannot accept this as a workaround because your clients will not have the ability to rebuild the libraries you distribute before they use them.
Cause
You had built the static library with the /GL (Whole Program Optimization) compiler switch, which requires Link Time Code Generation (/LTCG) when the static library is subsequently linked. These features require that all linked modules be built by the same version of the compiler. In fact, if precompiled headers are used, the same machine must build and link all the involved object code. Therefore, it is highly recommended that static libraries not be built with the /GL switch, since their intended use is quite frequently to support reuse by others.
Solution
You rebuilt the static library on your VS2008 SP1 machine without the /GL switch, and you no longer encounter this problem.
Please let me know if this info is helpful to you or not.
Regards,
Jialiang Ge
MSDN Subscriber Support in Forum
If you have any feedback of our support, please contact [email protected]
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.

Output mismatch between BEx query output and WebI Report output

Hi All,
I have a BEx query in which there are only characteristics placed in rows.
There are combinations of the values of the characteristics giving different records in the query output.
Date is one of the characterisctics in the query output.
There is an output mismatch between the query output and the WebI report output in the following case:
When there are 'Not Assigned' or '#' or blank values, there are additional entries(rows) in the WebI report, giving repeating or wrong entries in the Date field. This is incorrect data.
Is this because of the 'Not Assigned' or '#' or blank values of the Characteristics or is there any other reason?
How do I fix this?
Please helo me with this.
Thanks and Regards,
Srilakshmi B

Hi Rajesh,
I need to verify the WebI report output for records with # and 'Not assigned' values for the cHracteristics in the report.
So I cannot check the WebI report by hiding the # or Not assigned values.
The problem is that in the Query output the records are like these shown below:
Char1                    CHar2                          CHar3                       Date field
A                             B                                 C                                Date1
#(Not assgined)      #(Not assgined)      #(Not assgined)             No value
Where as the WebI report output is as below:
Char1                    CHar2                          CHar3                       Date field
A                             B                                 C                                Date1
#(Not assgined)      #(Not assgined)      #(Not assgined)            Date1
As shown here, there are wrong/repeating entries for the Date field in the WebI report output.
Please check this and let me know what could be the issue and how do I fix it.
Thanks and Regards,
Srilakshmi B

How to Reconcile Data Between SAP Source Systems and SAP NetWeaver BI

Hi,
I just read "How to Reconcile Data Between SAP Source Systems and SAP NetWeaver BI". While I'm waiting for more authorisation to r/3 to carry it out and test this functionality.
I'd like to ask a question to anyone who has implemented this type solution. On page 10 it talks about creating a view then setting up the datasource. The solution talks about runnig a query. I suspect when we run a query I would run it for only a period(using variable) to reconcile.
My question is this. Will the datasource extractor on /r3 only select the period in our variable or will it do a full selection of the data which would then be passed to BW for filtering?
Regards

DEar Mark,
There are several avenues where you can see and reconcile your data with source system, u can see data in by tcode RSA3 for a datasource, and compare the values with actual document posted into the R/3 system. Respective fuctional consultant canhelp you a lot to confirm the data.
On BW side u can see the data in PSA and then check tranformations which subsequent change/update/reject data records based on the selective conditions.
hope this helps.
Kindly assign the points if it works.
Revert back if u need futher help/information.

IDoc structure mismatch between SAP R/3 and PI

Similar Messages

Maybe you are looking for