CUP Initial data

Dear All
I have an issue with a CUP 5.3 SP13 install which I hope someone can help me with. I have loaded the initial files below in the sequence listed. This has given me the majority of default workflow types (Under Configuration>Miscellaneous) and the request types (Configuration>Request Configuration>Request Types).
However there are no workflow types for MITICTRL, MITIOBJ and RISK and the request types that use these workflow types are not there either.
I have tried reloading the files a number of times but it has not made any difference. Does anyone know if these files should be creating these entries and if not how to get them created?
AE_init_append_data.xml
AE_init_append_data_ForSODUARReview.xml
AE_init_clean_and_insert_data.xml
Thanks
Barry

Hello Barry
The initial data files that you are upload are relevant for AE only and you will get workflow type for AE only i.e. CUP
As per your requirement you want to create workflow for type MITICTRL, MITIOBJ and RISK which are related to CC (RAR).
To get these workflow type in AE (CUP) you need to integrate your CC (RAR) to AE (CUP) .
Kindly follow steps given in configuration guide (page no : 27 ,topic :Workflow Integration with Compliant User Provisioning) .
After doing this also double check that in AE (CUP) you have upload initial data (mentioned initially in your post) files for SP 13 as for every SP initial files will be different.
Hope this will solve your problem.
Thanks & Regards
Asheesh

Similar Messages

GRC AC v5.3 CUP - Initial Data Files

Hi All,
re: GRC AC v5.3 CUP - Initial Data Files
Our GRC-AC v5.3 CUP Dev system has too many roles and we want it to match our GRC-AC v5.3 CUP QA system. We do not want to go through one role at a time and delete them. Would it be the correct procedure to export the CUP QA system "Initial Data" files for "Roles" and import into CUP DEV using the setting "Clean and Insert".
Both systems are on the same CUP Version / SP / Build.
Any help on this would be greatly appreciated.
Thanks,
John

>
John Stephens wrote:
> Hi All,
>
> Yes, you are correct. An attempt gives the following error message:
>
> "x Please select Insert or Append option, to avoid Data Integrity errors, Clean and Insert option is not available."
>
> We came up with some additional options that we will pursue to resolve this.
>
> Thanks for your help on this.
>
> -john
Hi John,
Can you elaborate on what options you pursued to do mass role removal in CUP?
Thanks!
Jes

XEM - Unable to load the initial data or the variances(delta) data into sys

I am installing xEM 2.0 SP 10 (SAP xApp Emissions Management) in a windows environment with SQL 5000. I installed xEM on NW 2004, usage types AS Java and EP 6.
I am attempting to load the initial data or the variances (delta) data into the system. Instruction is on page 15 in the install guide.
I am supposed to enter the following in the command line:
java -Djava.ext.dirs=. -jar SAPtrans.jar import logfile=import.log datafile=init.dat connectstring=[JDBC Driver];[JDBCUrl];[User];[Password]
Example command for import into SQL Server:
java -Djava.ext.dirs=. -jar SAPtrans.jar import logfile=import.log datafile=init.dat connectstring=com.ddtek.jdbc.sqlserver.SQLServerDriver; jdbc:datadirect:sqlserver://vma03:1433;SAPC11DB;password
The customer I am with is running the xEM database on a different instance. This is where I run into a problem. I am not sure how to specify the instance in the script. This is what I have attempted so far:
C:\>cd temp\load
C:\Temp\load>java -Djava.ext.dirs=. -jar SAPtrans.jar import logfile=import.log datafile=init.dat connectstring=com.ddte
k.jdbc.sqlserver.SQLServerDriver;jdbc:datadirect:sqlserver://PRODSQL43:SQL3:1534;SAPPEMDB;password
java.lang.Exception: ERROR: Cannot connect to the database:ERROR: Connect failed to database jdbc:datadirect:sqlserver:/
/PRODSQL43:SQL3:1534 as user SAPPEMDB (java.sql.SQLException/[DataDirect][SQLServer JDBC Driver]Unable to connect. Inva
lid URL.): [DataDirect][SQLServer JDBC Driver]Unable to connect. Invalid URL.
        at com.sap.sdm.util.dbaccess.DBTask.dbImport(DBTask.java:356)
        at com.sap.sdm.util.dbaccess.SapTransTask.perform_import(SapTransTask.java:293)
        at com.sap.sdm.util.dbaccess.SapTransTask.execute(SapTransTask.java:51)
        at com.sap.sdm.util.dbaccess.SapTrans.main(SapTrans.java:21)
import aborted with java.lang.Exception: ERROR: Cannot connect to the database:ERROR: Connect failed to database jdbc:da
tadirect:sqlserver://PRODSQL43:SQL3:1534 as user SAPPEMDB (java.sql.SQLException/[DataDirect][SQLServer JDBC Driver]Unab
le to connect. Invalid URL.): [DataDirect][SQLServer JDBC Driver]Unable to connect. Invalid URL.
C:\Temp\load>java -Djava.ext.dirs=. -jar SAPtrans.jar import logfile=import.log datafile=init.dat connectstring=com.ddte
k.jdbc.sqlserver.SQLServerDriver;jdbc:datadirect:sqlserver://PRODSQL43;SQL3:1534;SAPPEMDB;password
java.lang.Exception: ERROR: Cannot connect to the database:ERROR: Connect failed to database jdbc:datadirect:sqlserver:/
/PRODSQL43 as user SQL3:1534 (java.sql.SQLException/[DataDirect][SQLServer JDBC Driver]Error establishing socket. Connec
tion refused: connect): [DataDirect][SQLServer JDBC Driver]Error establishing socket. Connection refused: connect
        at com.sap.sdm.util.dbaccess.DBTask.dbImport(DBTask.java:356)
        at com.sap.sdm.util.dbaccess.SapTransTask.perform_import(SapTransTask.java:293)
        at com.sap.sdm.util.dbaccess.SapTransTask.execute(SapTransTask.java:51)
        at com.sap.sdm.util.dbaccess.SapTrans.main(SapTrans.java:21)
import aborted with java.lang.Exception: ERROR: Cannot connect to the database:ERROR: Connect failed to database jdbc:da
tadirect:sqlserver://PRODSQL43 as user SQL3:1534 (java.sql.SQLException/[DataDirect][SQLServer JDBC Driver]Error establi
shing socket. Connection refused: connect): [DataDirect][SQLServer JDBC Driver]Error establishing socket. Connection ref
used: connect
C:\Temp\load>java -Djava.ext.dirs=. -jar SAPtrans.jar import logfile=import.log datafile=init.dat connectstring=com.ddte
k.jdbc.sqlserver.SQLServerDriver;jdbc:datadirect:sqlserver://PRODSQL43:1534;SQL3;SAPPEMDB;password
java.lang.Exception: ERROR: Cannot connect to the database:ERROR: Connect failed to database jdbc:datadirect:sqlserver:/
/PRODSQL43:1534 as user SQL3 (java.sql.SQLException/[DataDirect][SQLServer JDBC Driver][SQLServer]Login failed for user
'SQL3'.): [DataDirect][SQLServer JDBC Driver][SQLServer]Login failed for user 'SQL3'.
        at com.sap.sdm.util.dbaccess.DBTask.dbImport(DBTask.java:356)
        at com.sap.sdm.util.dbaccess.SapTransTask.perform_import(SapTransTask.java:293)
        at com.sap.sdm.util.dbaccess.SapTransTask.execute(SapTransTask.java:51)
        at com.sap.sdm.util.dbaccess.SapTrans.main(SapTrans.java:21)
import aborted with java.lang.Exception: ERROR: Cannot connect to the database:ERROR: Connect failed to database jdbc:da
tadirect:sqlserver://PRODSQL43:1534 as user SQL3 (java.sql.SQLException/[DataDirect][SQLServer JDBC Driver][SQLServer]Lo
gin failed for user 'SQL3'.): [DataDirect][SQLServer JDBC Driver][SQLServer]Login failed for user 'SQL3'.
C:\Temp\load>java -Djava.ext.dirs=. -jar SAPtrans.jar import logfile=import.log datafile=init.dat connectstring=com.ddte
k.jdbc.sqlserver.SQLServerDriver;jdbc:datadirect:sqlserver://PRODSQL43:1534:SQL3;SAPPEMDB;password
java.lang.Exception: ERROR: Cannot connect to the database:ERROR: Connect failed to database jdbc:datadirect:sqlserver:/
/PRODSQL43:1534:SQL3 as user SAPPEMDB (java.sql.SQLException/[DataDirect][SQLServer JDBC Driver]Unable to connect. Inva
lid URL.): [DataDirect][SQLServer JDBC Driver]Unable to connect. Invalid URL.
        at com.sap.sdm.util.dbaccess.DBTask.dbImport(DBTask.java:356)
        at com.sap.sdm.util.dbaccess.SapTransTask.perform_import(SapTransTask.java:293)
        at com.sap.sdm.util.dbaccess.SapTransTask.execute(SapTransTask.java:51)
        at com.sap.sdm.util.dbaccess.SapTrans.main(SapTrans.java:21)
import aborted with java.lang.Exception: ERROR: Cannot connect to the database:ERROR: Connect failed to database jdbc:da
tadirect:sqlserver://PRODSQL43:1534:SQL3 as user SAPPEMDB (java.sql.SQLException/[DataDirect][SQLServer JDBC Driver]Unab
le to connect. Invalid URL.): [DataDirect][SQLServer JDBC Driver]Unable to connect. Invalid URL.
C:\Temp\load>
My last attempt was a command using colons and semicolons with the following results. The closest (there was a significant delay before the error or failure) appears to have been //PRODSQL43;SQL3:1534; (second attempt). The error listed from this attempt is   "Error establishing socket. Connection refused: connect".
I also checked the default database that user SAPPEMDB has in place and it is assign the correct database.
Please help.
Message was edited by: Owner
        Mike Smayrabunya

Hey,
It looks like one of the following:
1. The DB is down,
2. The user SAPPEMDB does not have the right authorization.
3. The password of the user SAPPEMDB is not password
4. The syntax is incorrect
in order to find what is the problem,
please:
1. Login in the the DB PRODSQL43:1534 with the user "SAPPEMDB" and the password "password",
this will eliminate the options 1 - DB down, 2 -SAPPEMDB does not have authorization and 3 - password of the user SAPPEMDB is not password.
2. If the login failed, than please run sql trace with security elements (in the client there is a tool called "SQL Profiler"
3. If the login is correct, than you check the syntax of the command:
"java -Djava.ext.dirs=. -jar SAPtrans.jar import logfile=import.log datafile=init.dat connectstring=com.ddtek.jdbc.sqlserver.SQLServerDriver; jdbc:datadirect:sqlserver://vma03:1433;SAPC11DB;password"
According to the error message "Error establishing socket. Connection refused"
it looks like The DB is down or syntax is incorrect.

Best Practice for initial data

When installing a database onto a new server, I do not know what is the best solution to populate the database with the initial data that needs to exist before I can start running. I have sql scripts that take care of creating the tables, constraints, and triggers, but what is the best way to populate the database with my data?
I think that writing sql inserts seem a little complicated and writing a free standing program to interface with the database would take a little longer than I want. Is there a tool available to do my initial population?
Thanks in advance.

I have similar situation to yours where I have to install the database with starting data. What I have done to make this process easier is that I have set up a schema that is an exact replica of what is out in production. This schema has all of the required data in which the application needs to order to be functional. I keep this schema updated with all changes. When the time comes to create another database I just export this schema and import it into the new database. The seed data is small so the export is small as well. This approach has saved me a lot of time in the new deployments.

Require help to solve Connection timed out error while reload initial data

Dear Developers,
I have installed SAP NetWeaver and SAP ME SDK 2.0 on my laptop and working from offshore, the SAP ME WIP and ODS database is situated at onsite. The installation is working fine, however, after developing Activity Hooks, at the step where I need to Reload Initial Data for the Site where I want the Activity to be used I get the below error message:
500 Connection timed out
Error: -5
Version: 7011
Component: ICM
Date/Time: Wed Mar 07 12:37:38 2012
Module: icxxthr.c
Line: 4184
Server: <laptop_hostname>_<SID>_00
Error Tag: {-}
Detail: Connection to partner timed out after 600s
© 2001-2009, SAP AG
How to find out what is causing this error? When I use the hostname of the onsite SAP ME application pointing to the same database, Reload Initial Data works fine. I need to reload initial data from laptop SAP ME application only, beacause the activity hook classes reside on my laptop, before I send the SAPME.sca files for common server build.

Hello,
Please try to increase PROCTIMEOUT ICM parameter for the corresponding server\port. If it does not help, please, check NW default traces for ME errors and share your results with us.
Best regards,
Alex.

Report with reportData tag stil user the initial data

I have created a report based upon a file, this works fine.
when I want to schedule it using the <reportData>...</reportData> tag it still uses my initial data.
The data that is provided is encode.
This is my soap envelope:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<pub:scheduleReport xmlns:pub="http://xmlns.oracle.com/oxp/service/PublicReportService">
<scheduleRequest>
<deliveryRequest>
<printOption>
<printerName>Ontwik</printerName>
<printNumberOfCopy>1</printNumberOfCopy>
<printTray>Tray 2</printTray>
<printSide>Double Sided Long Edge (Duplex)</printSide>
</printOption>
</deliveryRequest>
<reportRequest>
<attributeFormat>pdf</attributeFormat>
<attributeTemplate>DefaultTemplate</attributeTemplate>
<reportAbsolutePath>/~administrator/basedonFile/basedonFile.xdo</reportAbsolutePath> <reportData>50453576626C4E6F615842745A573530506A784462476C6C626E512B50474669596E4A6C646D6C6864476C76626A34354F544D3350433968596D4A795A585A700D0A595852706232342B504535686257552B51695A686258413755794242546C525852564A515043394F5957316C506A7776513278705A573530506A784A5A4756750D0A64476C6D61574E6864476C76626A3551515535454D446B7A4E5459794D444D384C306C6B5A57353061575A705932463061573975506A786862573931626E512B0D0A4D6A51334E4449344D7A77765957317664573530506A784F645731695A584A505A6B6C305A57317A506A457A4D6A7776546E5674596D567954325A4A644756740D0A637A3438546C4E514C55465556464A4A516C565552564D2B50464E5A553052424C564E356333526C5A57316B59585231625434784E79314B565577744D6A41770D0A4F54777655316C545245457455336C7A6447566C6257526864485674506A7856546B6C554C57566C626D686C6157512B517A77765655354A5643316C5A57356F0D0A5A576C6B506A785454314A555279317A623239796443426E6232566B5A584A6C626A354852447776553039535645637463323976636E51675A32396C5A4756790D0A5A57342B50464242546B52484C584268626D52325A584A7A64484A6C6132746C636A34354F544D335043395151553545527931775957356B646D5679633352790D0A5A5774725A58492B5045684A553152504C55687063335276636D6C6C617A34384C30684A553152504C55687063335276636D6C6C617A343856466C51543049740D0A64486C775A5342685A6D64705A6E526C596D56336157707A506C41384C31525A554539434C5852356347556759575A6E61575A305A574A6C64326C71637A34380D0A51306843525667745132686C59327469623367675A5868775A584A3061584E6C506C6B384C304E49516B56594C554E6F5A574E72596D393449475634634756790D0A64476C7A5A54343851306843533038745132686C59327469623367676132397A64475675506C6B384C304E49516B74504C554E6F5A574E72596D3934494774760D0A6333526C626A34384C303554554331425646525353554A5656455654506A7776546D3975553268706347316C626E512B</reportData><sizeOfDataChunkDownload>-1</sizeOfDataChunkDownload>
</reportRequest>
<userJobName>PrintJobs</userJobName></scheduleRequest><userID>Administrator</userID><password>XXXXXXXXXXX</password>
</pub:scheduleReport>
</soapenv:Body>
</soapenv:Envelope>
any one has a cleu ?

same here; if i run runReport it works okay..when is use ScheduleReport it shows the intial data(preview)
Do you already know of a solution?

Error while running PB40 - initial data entry action

Hi Friends,
I am running PB40 initial data entry action. The values that I am giving in the Personnel Officer field are not getting accepted.
Its giving me error : *Entry does not exist in T526 (check entry)*
I have checked T526 table in SE16 and its showing me all the values that have been maintained for my administrator group APPL.
"PINCH" feature is also maintained where the Tclas B- applicant data has value APPL.
In SU3 also, I have maintained SGR - APPL.
Please advise what else cab done to correct this error.

reema
have u activated switch between OM and Personal office
PPVAC PREF just check it out and let me know

Problem Initializing data-source oc4j

Hi,
When starting the oc4j container I get the following error.
ora03 $ Error initializing data-source 'jdbc/OracleCoreDS': DriverManagerDataSource driver 'oracle.jdbc.driver.OracleDri
ver' not found
Error initializing data-source 'jdbc/css_userCoreDS': DriverManagerDataSource driver 'oracle.jdbc.driver.OracleDriver' n
ot found
Error initializing data-source 'jdbc/AnteDateCoreDS': DriverManagerDataSource driver 'oracle.jdbc.driver.OracleDriver' n
ot found
Warning: Error reading transaction-log file (/u01/web/ias102/j2ee/home/persistence/transaction.state) for recovery: prem
ature end of file
Forced or abrubt (crash etc) server shutdown detected, starting recovery process...
Recovery completed, 0 connections committed and 0 rolled back...
Oracle9iAS (1.0.2.2.1) Containers for J2EE initialized
Here is my data-sources.xml
<?xml version = '1.0' encoding = 'windows-1252'?>
<!DOCTYPE data-sources PUBLIC "Orion data-sources" "http://xmlns.oracle.com/ias/dtds/data-sources.dtd">
<data-sources>
<data-source
     class="com.evermind.sql.DriverManagerDataSource"
     connection-driver="oracle.jdbc.driver.OracleDriver"
     ejb-location="jdbc/css_userDS"
     inactivity-timeout="30"
     location="jdbc/css_userCoreDS"
     name="css_userDS"
     password="css"
     url="jdbc:oracle:thin:@oradev01.nf.prv:1521:css"
     username="css_user"
     xa-location="jdbc/xa/css_userXADS"/>
<data-source
     class="com.evermind.sql.DriverManagerDataSource"
     connection-driver="oracle.jdbc.driver.OracleDriver"
     ejb-location="jdbc/AnteDateDS"
     inactivity-timeout="30"
     location="jdbc/AnteDateCoreDS"
     name="AnteDateDS" password="date"
     url="jdbc:oracle:thin:@oradev01.nf.prv:1521:test"
     username="antedate"
     xa-location="jdbc/xa/AnteDateXADS"/>
</data-sources>
I have made sure that the classes12.zip in in my CLASSPATH. OS HP-UX 11.00. Help!!!

David,
OC4J does not pickup the CLASSPATH from $CLASSPATH env variable. Do you have the classes12.zip in $OC4J_HOME/j2ee/home/lib directory?
If not can you please put that in that directory and restart your server.
regards
Debu Panda
Oracle

2lis_03_um initial data load

Dear Consultants,
Our r/3 system is very busy.So I don't want to stop the r/3 system to extract the stock data.Is there any way to do it.I mean Can I extract the initial data while r/3 system is running.I am worrying about loosing the data.
Best regards

Hi,
In case of V3 update of Queue Delta update methodes,We have to lock the users when we are filling the setup tables. But in cese of Direct Delta update Mode, we need to lock the R/3 users until we complete both Filling set uptale and Delta init.
For more information on all these Methods, take a look on the note: 505700
<i>1. Why should I no longer use the "Serialized V3 update" as of PI 2002.1 or PI-A 2002.1?
The following restrictions and problems with the "serialized V3 update" resulted in alternative update methods being provided with the new plug-in and the "serialized V3 update" update method no longer being provided with an offset of 2 plug-in releases.
a) If, in an R/3 System, several users who are logged on in different languages enter documents in an application, the V3 collective run only ever processes the update entries for one language during a process call. Subsequently, a process call is automatically started for the update entries from the documents that were entered in the next language. During the serialized V3 update, only update entries that were generated in direct chronological order and with the same logon language can therefore be processed. If the language in the sequence of the update entries changes, the V3 collective update process is terminated and then restarted with the new language.
For every restart, the VBHDR update table is read sequentially on the database. If the update tables contain a very high number of entries, it may require so much time to process the update data that more new update records are simultaneously generated than the number of records being processed.
b) The serialized V3 update can only guarantee the correct sequence of extraction data in a document if the document has not been changed twice in one second.
c) Furthermore, the serialized V3 update can only ensure that the extraction data of a document is in the correct sequence if the times have been synchronized exactly on all system instances, since the time of the update record (which is determined using the locale time of the application server) is used in sorting the update data.
d) In addition, the serialized V3 update can only ensure that the extraction data of a document is in the correct sequence if an error did not occur beforehand in the U2 update, since the V3 update only processes update data, for which the U2 update is successfully processed.
2. New "direct delta" update method:
With this update mode, extraction data is transferred directly to the BW delta queues every time a document is posted. In this way, each document posted with delta extraction is converted to exactly one LUW in the related BW delta queues.
If you are using this method, there is no need to schedule a job at regular intervals to transfer the data to the BW delta queues. On the other hand, the number of LUWs per DataSource increases significantly in the BW delta queues because the deltas of many documents are not summarized into one LUW in the BW delta queues as was previously the case for the V3 update.
If you are using this update mode, note that you cannot post any documents during delta initialization in an application from the start of the recompilation run in the OLTP until all delta init requests have been successfully updated successfully in BW. Otherwise, data from documents posted in the meantime is irretrievably lost.
The restrictions and problems described in relation to the "Serialized V3 update" do not apply to this update method.
This update method is recommended for the following general criteria:
a) A maximum of 10,000 document changes (creating, changing or deleting documents) are accrued between two delta extractions for the application in question. A (considerably) larger number of LUWs in the BW delta queue can result in terminations during extraction.
b) With a future delta initialization, you can ensure that no documents are posted from the start of the recompilation run in R/3 until all delta-init requests have been successfully posted. This applies particularly if, for example, you want to include more organizational units such as another plant or sales organization in the extraction. Stopping the posting of documents always applies to the entire client.
3. The new "queued delta" update method:
With this update mode, the extraction data for the affected application is compiled in an extraction queue (instead of in the update data) and can be transferred to the BW delta queues by an update collective run, as previously executed during the V3 update.
Up to 10,000 delta extractions of documents to an LUW in the BW delta queues are cumulated in this way per DataSource, depending on the application.
If you use this method, it is also necessary to schedule a job to regularly transfer the data to the BW delta queues ("update collective run"). However, you should note that reports delivered using the logistics extract structures Customizing cockpit are used during this scheduling. There is no point in scheduling with the RSM13005 report for this update method since this report only processes V3 update entries. The simplest way to perform scheduling is via the "Job control" function in the logistics extract structures Customizing Cockpit. We recommend that you schedule the job hourly during normal operation - that is, after successful delta initialization.
In the case of a delta initialization, the document postings of the affected application can be included again after successful execution of the recompilation run in the OLTP, provided that you make sure that the update collective run is not started before all delta Init requests have been successfully updated in the BW.
In the posting-free phase during the recompilation run in OLTP, you should execute the update collective run once (as before) to make sure that there are no old delta extraction data remaining in the extraction queues when you resume posting of documents.
If you want to use the functions of the logistics extract structures Customizing cockpit to make changes to the extract structures of an application (for which you selected this update method), you should make absolutely sure that there is no data in the extraction queue before executing these changes in the affected systems. This applies in particular to the transfer of changes to a production system. You can perform a check when the V3 update is already in use in the respective target system using the RMCSBWCC check report.
In the following cases, the extraction queues should never contain any data:
- Importing an R/3 Support Package
- Performing an R/3 upgrade
- Importing a plug-in Support Packages
- Executing a plug-in upgrade
For an overview of the data of all extraction queues of the logistics extract structures Customizing Cockpit, use transaction LBWQ. You may also obtain this overview via the "Log queue overview" function in the logistics extract structures Customizing cockpit. Only the extraction queues that currently contain extraction data are displayed in this case.
The restrictions and problems described in relation to the "Serialized V3 update" do not apply to this update method.
This update method is recommended for the following general criteria:
a) More than 10,000 document changes (creating, changing or deleting a documents) are performed each day for the application in question.
b) In future delta initializations, you must reduce the posting-free phase to executing the recompilation run in R/3. The document postings should be included again when the delta Init requests are posted in BW. Of course, the conditions described above for the update collective run must be taken into account.
4. The new "unserialized V3 update" update method:
With this update mode, the extraction data of the application in question continues to be written to the update tables using a V3 update module and is retained there until the data is read and processed by a collective update run.
However, unlike the current default values (serialized V3 update), the data is read in the update collective run (without taking the sequence from the update tables into account) and then transferred to the BW delta queues.
The restrictions and problems described in relation to the "Serialized V3 update" do not apply to this update method since serialized data transfer is never the aim of this update method. However, you should note the following limitation of this update method:
The extraction data of a document posting, where update terminations occurred in the V2 update, can only be processed by the V3 update when the V2 update has been successfully posted.
This update method is recommended for the following general criteria:
a) Due to the design of the data targets in BW and for the particular application in question, it is irrelevant whether or not the extraction data is transferred to BW in exactly the same sequence in which the data was generated in R/3.
5. Other essential points to consider:
a) If you want to select a new update method in application 02 (Purchasing), it is IMPERATIVE that you implement note 500736. Otherwise, even if you have selected another update method, the data will still be written to the V3 update. The update data can then no longer be processed using the RMBV302 report.
b) If you want to select a new update method in application 03 (Inventory Management), it is IMPERATIVE that you implement note 486784. Otherwise, even if you have selected another update method, the data will still be written to the V3 update. The update data can then no longer be processed using the RMBWV303 report.
c) If you want to select a new update method in application 04 (Production Planning and Control), it is IMPERATIVE that you implement note 491382. Otherwise, even if you have selected another update method, the data will still be written to the V3 update. The update data can then no longer be processed using the RMBWV304 report.
d) If you want to select a new update method in application 45 (Agency Business), it is IMPERATIVE that you implement note 507357. Otherwise, even if you have selected another update method, the data will still be written to the V3 update. The update data can then no longer be processed using the RMBWV345 report.
e) If you want to change the update method of an application to "queued delta", we urgently recommended that you install the latest qRFC version. In this case, you must refer to note 438015.
f) If you use the new selection function in the logistics extract structures Customizing Cockpit in an application to change from the "Serialized V3" update method to the "direct delta" or "queued delta", you must make sure that there are no pending V3 updates for the applications concerned before importing the relevant correction in all affected systems. To check this, use transaction SA38 to run the RMCSBWCC report with one of the following extract structures in the relevant systems:
    Application 02:   MC02M_0HDR
    Application 03:   MC03BF0
    Application 04:   MC04PE0ARB
    Application 05:   MC05Q00ACT
    Application 08:   MC08TR0FKP
    Application 11:   MC11VA0HDR
    Application 12:   MC12VC0HDR
    Application 13:   MC13VD0HDR
    Application 17:   MC17I00ACT
    Application 18:   MC18I00ACT
    Application 40:   MC40RP0REV
    Application 43:   MC43RK0CAS
    Application 44:   MC44RB0REC
    Application 45:   MC45W_0HDR.
You can switch the update method if this report does return any information on open V3 updates. Of course, you must not post any documents in the affected application after checking with the report and until you import the relevant Customizing request. This procedure applies in particular to importing the relevant Customizing request into a production system.
Otherwise, the pending V3 updates are no longer processed. This processing is still feasible even after you import the Customizing request using the RSM13005 report. However, in this case, you can be sure that the serialization of data in the BW delta queues has not been preserved.
g) Early delta initialization in the logistics extraction:
As of PI 2002.1 and BW Release 3.0B, you can use the early delta initialization to perform the delta initialization for selected DataSources.
Only the DataSources of applications 11, 12 and 13 support this procedure in the logistics extraction for PI 2002.1.
The early delta initialization is used to admit document postings in the OLTP system as early as possible during the initialization procedure. If an early delta initialization InfoPackage was started in BW, data may be written immediately to the delta queue of the central delta management.
When you use the "direct delta" update method in the logistics extraction, you do not have to wait for the successful conclusion of all delta Init requests in order to readmit document postings in the OLTP if you are using an early delta initialization.
When you use the "queued delta" update method, early delta initialization is essentially of no advantage because here, as with conventional initialization procedures, you can readmit document postings after successfully filling the setup tables, provided that you ensure that no data is transferred from the extraction queue to the delta queue, that is, an update collective run is not triggered until all of the delta init requests have been successfully posted.
Regardless of the initialization procedure or update method selected, it is nevertheless necessary to stop any document postings for the affected application during a recompilation run in the OLTP (filling the setup tables).</i>
With rgds,
Anil Kumar Sharma .P

Runtime error while creating applicent initial data in PB10

Dear friends,
       in initial data entry in reruitment in PB10 once i complete the entry of data in organization assignment.it is going into ABAP runtime error.
Trigger Location of Runtime Error
    Program                               SAPLHRAC
    Include                                 LHRACU05
    Row                                     390
    Module type                         (FORM)
    Module Name                        READ_IT_FROM_DB
Short text
    Exception condition "INFTY_NOT_FOUND" raised.
can any help me how to resolve this issue.
Thanks in advance,
Regards,
sai prasad

Hi Revathi,
    With reference to your responce i have checked pb04. all that i found is it is not taking the number range that i have assigned in NUMAP feature it is taking other number range.
How should i go further with this.
Regards,
sai prasad

How to fill depended Z-Table, created by Rapid Application Tool, with initial data?

Hello gurus,
I created a component ZBOOKING with RAD Tool and will fill booking detail table with initial data during a creation of new booking objekt.
My Booking component looks like on the picture below. It was created with Rapid Application Tool and is based on one ZBOOKING Table with was created in CRM Backend and one “Booking details” Table with was created with Rapid Application.
My Question is how should I populate initial Template-Data to this dependent “booking details” Table wenn I will create a new booking object.
Web UI of ZBooking component
Component structure of ZBooking
I have tried to do sample implementation in do_init_context method of ZACL_CLASS00000C_IMPL class to fill ZBOOKING_DETAILS with some data.
method DO_INIT_CONTEXT.
CALL METHOD SUPER->DO_INIT_CONTEXT.
DATA: lr_col TYPE REF TO if_bol_bo_col,
lr_valuenode TYPE REF TO cl_bsp_wd_value_node,
lr_template TYPE REF TO ZBOOKING_DETAIL.
CREATE DATA lr_template.
CREATE OBJECT lr_valuenode
EXPORTING
IV_DATA_REF = lr_template.
if lr_valuenode is BOUND.
lr_valuenode->SET_PROPERTY_AS_STRING(
iv_attr_name = 'ZZVISITDATE' "#EC NOTEXT
iv_value     = '01.01.2014'
ENDIF.
CREATE OBJECT lr_col TYPE cl_crm_bol_bo_col.
lr_col->ADD(
exporting
iv_entity = lr_entity
IV_SET_FOCUS = ABAP_TRUE
me->TYPED_CONTEXT->ZBOOKING_DETAIL->SET_COLLECTION( lr_col ).
endmethod.
After this implementation the initial data is displayed in “Booking details”.
However if I press an Edit-List-button (Assignment block) I get an error “CUST Operation”.
May be I should fill this depented table ZBOOKING_DETAILS without cl_bsp_wd_value_node?
Where should I implement logic if I want to fill initial data just during creation of booking object and not every
time when the booking object is called or initialized?
Regards Dmitry

Hi,
I get an error "Dereferencing of the NULL reference" during created_related_entity.
If you see on the picture below I think that I use right relation name for my zbooking_detail table.
method DO_INIT_CONTEXT.
CALL METHOD SUPER->DO_INIT_CONTEXT.
data :   lr_leading_entity TYPE REF TO cl_crm_bol_entity,
            lr_col TYPE REF TO if_bol_bo_col.
           lr_leading_entity->create_related_entity(
                  iv_relation_name = 'ZAET_CA_ATAB000000' ).
           lr_leading_entity->SET_PROPERTY_AS_STRING(
                       iv_attr_name = 'ZZVISITDATE' "#EC NOTEXT
                       iv_value     = '01.01.2014'
lr_col->ADD(
   exporting
     iv_entity = lr_leading_entity
     IV_SET_FOCUS = ABAP_TRUE
me->TYPED_CONTEXT->ZBOOKING_DETAIL->SET_COLLECTION( lr_col ).
endmethod.
Many Thanks & Regards,
Dmitry

Change language after load initial data (ME 5.2)

Hello,
we have an ME system installed with german language settings in the Netweaver config tool. We would like to change this english. I found in the installation guide the following remark:
The u2013Duser.country and u2013Duser.language values must be set to the single, supported language
for the SAP ME installation and cannot be modified after initial data has been loaded in SAP ME in
the Loading Initial Data section below. For more information, see your SAP ME consultant.
Can you tell the tables which need to be changed?
Regards,
Kai

Hi,
You can change language in netwear level SAP Basis people can do that this setting.
Thanks,
Ramesh

Initial data entry

hai
iam new to this community and iam new to sap
in initial data entry iam getting an option called cuil cuit wht is it and how to remove it
theja

manoj
i have goen into sm 30 and given the tables but it is goin g to employee permessibiliy screen is there any other way to de activate the cuil and cuit because iam a fresher.
points will be rewarded
theja

OIM Initial Data Load - Suggestion Please

Hi,
I have the following scenario :
1.My client is currently having 2 systems 1.AD and 2.HR application.
2.HR application is having only Employee Information.(it contains information like firstname,lastname,employeenumber etc)
3.AD is having both employees and contractor information
4.Client wanted my HR application to be the trusted source but the IDM login ID of existing users should be same us that of AD samaccount name.
I am using OIM 9.0 and 9041 connector pack.What would be the best way to do the initial data loading in this case?.Thanks in advance.

Hi,
Can you tell me how do you relate employee in HR to corresponding record in AD.Then I will be in better situation to explain how you can do it.
But even without this information following approach will solve your requirment.
1.Do the trusted recon from AD.
2.samAccountName will be mapped to user id field of OIM profile.
3.Do the trusted recon with HR.The matching key should be the answer of my above question.
4.For trusted recon with HR remove the Action "Create User" on No Match Found event.
Hope this will help.
Regards
Nitesh
Regards
Nitesh

Missing file: /private/etc/cups/ppds.dat

Cannot open my printer's utility - Lexmark z23 - All was well, then we updated to 10.4.5.
I know this file is missing: /private/etc/cups/ppds.dat
Any thoughts on where I might access it would be appreciated, or, confirm for me I'm gonna have to slog thru all the packages on the original install cds to find it.... : - 0
Thank you!!!!
YES, I read archived threads and know all about Miguel; - )

Geez Greg - Thanx for your time but that response is
almost insulting - Try restarting? That's like number
one on the newbie hit parade dude, right along
starting up holding down the shift key or running
fsck -y. Thanks for trying.
And your response is supposed to make others want to reply?
Anyone else? Please. I'm starting to think I got
screwed from using this printer when I upgraded my OS.
A quick search indicates that Greg is correct that the file in question is built by cupsd as needed. Surprised? I'm not. You could have restarted your computer several times in the amount of time it took you to post your rant.
If you don't want to restart your computer, then just restart CUPS. If that doesn't work, reset the printing system from the Printer Setup Utility. You can also search and search through the installation disks. You won't find that file, however. CUPS gets installed as part of the Essentials.pkg. The ppds.dat file, however, is not a file that gets installed.
Back to your original post -- I don't see a connection that would lead to a conclusion that the missing ppds.dat file is causing your printer's utility not to open. Even when you restore the ppds.dat file, you may not be able to open the utility for some other reason.
Matt
Mac Mini; B&W G3/300

CUP Initial data

Similar Messages

Maybe you are looking for