Hiring Process for US - BP for HR Administrator

I have a requirement to enable Hiring (US) in EP 7.0. We installed the business package and all the pre requisites are done. When I execute the process, I am able to send the form. But the infotypes are updated.
We are not integrating e-Recruitment and XI still I want to execute the process as a HR Administrator. Can anyone help me with configuration steps for running this process. The backend is ECC 6.0
Thanks in Advance
Rao Kavuri

Hi,
Pl check the Business Package structure under the correct BP version in this link
http://help.sap.com/saphelp_erp2005vp/helpdata/en/43/1d63953fce3566e10000000a11466f/frameset.htm
Regards
Srini

Similar Messages

ABAP MESSAGE_TYPE_X -DUmp Due to Change in hiring process for HK ?

Hi,
I changed the Hiring process , just added new infotype 0105 into the process for HK , after that i got an ABAP "MESSAGE_TYPE_X" dump when i tried to save PA30 .
See the below Error :
with the key 50002134567880       9999123119712134256206528473C_VBA in
table PA0342. It is possible that the record does not exist. The
following are a few of the possible causes for this:
o   The code in table PA0342 is not correctly specified in the data
    dictionary (SE11). Compare with another PAnnnn table.
o   An infotype may have an additional view infotype for which the
    record is not available. This situation can occur when system
    settings for infotype views (T582V) are changed.
o   Problems with database.
o   There may be other causes.

Try running the report rpu03420 for that pernr. Anyway 0342 is an infotype specific to HongKong.
~Suresh

Are there any rough processes for Solaris administrator to setup Sun LDAP as nameing server at Sun sparc host? like: 1st: modify /etc/nfsswitch.nfs 2nd: add LDAP server in /etc/hosts. 3rd: ......

Besides, can we install the LDAP server in sparc hosts as nameing system? Can we use Sun LDAP server or iPlanet Directory Server? or need BIND DNS server too?

There is a nice book from Michael Haines and Tom Bialaski: "Solaris and LDAP Naming Services" which contains all you need to configure Directory Server, LDAP, Naming Switch...
Ludovic.

OIM: Error while deploying Custom Approval Process for Self-Register

While deploying the Custom Approval Process for Self-Register, i am getting the following error in scac.log file
Nov 16, 2011 2:48:58 PM oracle.fabric.common.wsdl.SchemaManager isIncrementalBuildSupported
INFO: XMLSchema incremental build enabled.
Nov 16, 2011 2:48:58 PM com.collaxa.cube.CubeLogger info
INFO: validating "ApprovalProcess.bpel" ...
oracle.jrf.UnknownPlatformException: JRF is unable to determine the current application server platform.
     at oracle.jrf.ServerPlatformSupportFactory.getInstance(ServerPlatformSupportFactory.java:79)
     at oracle.integration.platform.blocks.WLSPlatformConfigurationProvider.<clinit>(WLSPlatformConfigurationProvider.java:44)
     at oracle.integration.platform.blocks.FabricConfigManager.<clinit>(FabricConfigManager.java:155)
     at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.loadXpathFunctions(FabricXPathFunctionResolver.java:271)
     at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.loadXPathConfigFile(FabricXPathFunctionResolver.java:153)
     at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.init(FabricXPathFunctionResolver.java:51)
     at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.loadFabricXpathFunctions(BPELXPathFunctionNameResolver.java:57)
     at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.<init>(BPELXPathFunctionNameResolver.java:48)
     at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.<clinit>(BPELXPathFunctionNameResolver.java:44)
     at com.collaxa.cube.lang.compiler.bpel.XPathExprValidatorVisitor.<init>(XPathExprValidatorVisitor.java:122)
     at com.collaxa.cube.lang.compiler.bpel.AssignValidator.<init>(AssignValidator.java:89)
     at com.collaxa.cube.lang.compiler.bpel.BpelParser.<init>(BpelParser.java:452)
     at com.collaxa.cube.lang.compiler.bpel.BPELValidator.validate(BPELValidator.java:60)
     at com.collaxa.cube.lang.compiler.BPEL1Processor.validate(BPEL1Processor.java:329)
     at com.collaxa.cube.lang.compiler.BPEL1Processor.process(BPEL1Processor.java:153)
     at com.collaxa.cube.lang.compiler.CubeParserHelper.compile(CubeParserHelper.java:47)
     at oracle.fabric.bpel.bpelc.BPELComponentValidator.validate(BPELComponentValidator.java:40)
     at oracle.soa.scac.ValidateComposite.validateComponentTypeServicesReferences(ValidateComposite.java:1117)
     at oracle.soa.scac.ValidateComposite.doValidation(ValidateComposite.java:500)
     at oracle.soa.scac.ValidateComposite.run(ValidateComposite.java:150)
     at oracle.soa.scac.ValidateComposite.main(ValidateComposite.java:135)
Nov 16, 2011 2:49:00 PM CubeProcessGenerator compile
WARNING: classpath is: D:\JDev11g\Middleware\jdeveloper\jdev\extensions\oracle.sca.modeler.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;D:\JDev11g\Middleware\oracle_common\modules\oracle.fabriccommon_11.1.1\fabric-common.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.mediator_11.1.1\mediator_client.jar;D:\JDev11g\Middleware\oracle_common\modules\oracle.mds_11.1.1\mdsrt.jar;D:\OIMPS1\Middleware\oracle_common\modules\oracle.jps_11.1.1\jps-manifest.jar;;D:\OIMPS1\Middleware\Oracle_IDM1\server\workflows\new-workflow\process-template\SelfRegistrationApprovalApp\SelfRegistrationApproval\SCA-INF\classes;D:\OIMPS1\Middleware\Oracle_IDM1\server\workflows\new-workflow\process-template\SelfRegistrationApprovalApp\SelfRegistrationApproval\SCA-INF\classes;D:\OIMPS1\Middleware\Oracle_IDM1\server\workflows\new-workflow\process-template\SelfRegistrationApprovalApp\SelfRegistrationApproval\SCA-INF\gen-classes;D:\OIMPS1\Middleware\Oracle_IDM1\server\workflows\new-workflow\process-template\SelfRegistrationApprovalApp\SelfRegistrationApproval\SCA-INF\lib\oimclient.jar;D:\JDev11g\Middleware\oracle_common\modules\commonj.sdo_2.1.0.jar;D:\JDev11g\Middleware\oracle_common\modules\oracle.fabriccommon_11.1.1\fabric-common.jar;D:\JDev11g\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xmlparserv2.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpel1-1-xbeans.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-common.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpel_coherence_config.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-exts.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\thirdparty.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpm-analytics.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-thirdparty.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\wsif-binding.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-validator.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\monitor-rt-xbean.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\oracle.soa.bpmn.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\user-patch.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.thirdparty.jar;D:\JDev11g\Middleware\jdeveloper\uddi\lib\oracle.soa.uddi.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\bpm-infra.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\testfwk-xbeans.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-ext.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-infra-scheduler.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\xmlunit-1.1.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-infra-tools.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-xpath-exts.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\oracle-soa-client-api.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.wls.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-client.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime-ext-was.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime-ext-wls.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\oracle.soa.fabric.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.workflow_11.1.1\bpm-services.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.ext_11.1.1\classes
In scac_out.xml file following is the error message
<Fault>
<severity>error</severity>
<loc>/ns:composite</loc>
<line/>
<col/>
<file/>
<msg>
<![CDATA[SCAC-50012]]>
</msg>
</Fault>

Hi,
I have run into the same problem with SOA 11.1.1.5 version. In my case after fixing the following two errors it seems to work fine.
If you have followed the guide, there must be some errors:
First the java code if copied then contains an extra enter value:
Instead of:
"try {
System.out.println("Prototype for invoking an OIM API from a SOA Composite");
System.out.println("RTM Usecase: Self Registration Approval by Organization
Administrator");"
Use the following:
"try {
System.out.println("Prototype for invoking an OIM API from a SOA Composite");
System.out.println("RTM Usecase: Self Registration Approval by Organization Administrator");"
The other error is that you should not use <BEAHOME>/oracle_common/modules/oracle.jps_11.1.1/jps-manifest.jar, but the <BEAHOME>/oracle_common/modules/oracle.jps_11.1.1/jps-api.jar in jdeveloper. After these the deployment to the application server works fine for me.

I keep getting a popup that says"host process for window services has stopped"

hp s5220f
microsoft windows 7 home premium edeition (64 bit)
I keep getting a popup window that says "host process for window services has stopped"
How can I get rid of this?

Hello tribefanz,
Sounds like a compatiblity issue with a program and Windows 7. We need to find out what program is causing the issue though. We can do that through event viewer
1. Click the start orb
2. Select Control Panel
3. System and Security
4. Under Administrative Tools select the Event Viewer
In the event viewer you will want to drill down into the Application and System logs and look for anything with a Red X that says Error. Identify the program causing the problem and then we can go from there.
If I have helped you in any way click the Kudos button to say Thanks.
The community works together, click Accept as Solution on the post that solves your issue for other members of the community to benefit from the solution.
- Friendship is magical.

Alert generation process for failed explorer infospaces

Hi, I am looking for an alert or mail generation process by which the Business Objects Administrator will get information about the explorer info space for which indexing has been failed , is there any way( script, event viewer) by which and alert will be send to Administrator inbox which contains the name of failed info space, Basically want to know the best practice to monitor daily info space indexing which saves time and effort.
Environment is SAP BO BI platform 4.0 SP08,
BO Explorer 4.0 SP08,
OS is Windows 2008.

Hello Isaac,
Have you tried typing in a specific system ID (e.g. DEV, PRD)? Does it then work? What Support Pack level are you running?
Please see OSS Note 1435605 and the related notes to it. It may help.
Best Regards, Dylan

What is the internal processing for idocs

Dear friends this is subbu working as a abap consultant.
can any body explain the how idocs are transfered (inbound process and outbound process)

1.Here out bound means sender.Inbound mens --receiver.
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
There are two filtering in IDoc.
Segment Filtering:
Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.
Data Filtering:
Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
Please check this link for more information.
http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
Reward points..

Expense reports are not processing for future date?

hi folks,
in our co.expense reports are not processing for future date, even though the end date is one month from now the expense reports are not getting paid.
can anybody assist me to come out of this issue.
thanks in advance,
regards
bhanu

HI,
Could you please share how to go Debug mode in Dymanic program, I have scenarion in SAP HR , when Employee is hire , during the hiring action Infotype 32 is updating based on following conditions
********INSERT IT0032 FOR CANDIDATE ID *************
P0001-PERSG<>'5' - True
P0000-MASSN='01'/X
P0000-MASSN='H1'/X
P0000-MASSN<>'84'/X
P0000-MASSN<>'86'/X
P0000-MASSN<>'99'/X
GET_PNALT(ZHR_CREATEP0032)
RP50D-FIELDS <> ''
INS,0032,,,(P0000-BEGDA),(P0000-ENDDA)/D
P0032-PNALT=RP50D-FIELD1
P0032-ZZ_COMPID='05' _ True
Infotype record is being created but there is no data in "RP50D-FIELD1 , so i tried to debug the subroutine GET_PNALT(ZHR_CREATEP0032) as mention in Dynamic action, its not going in debugger mode.
Do you have any Idea about how to debug the program. used in dynamic action
Regards,
Madhu

Standard process for creating a new version of an existing report

Hi All,
We are using Siebel 8.1 with BI Publisher.
Does any one know the standard process for creating a new version of an existing report - ie if 'BIP Report XXX' is created and works correctly from the siebel view but then an enhancement is developed, how is the enhancement deployed so that the new version completely replaces the old?
One suggestion was:
You can upload a new version of an existing report. You have to navigate to Administration - BIP > Report Template Registration... search for the report you need to replace (I would say that the new rtf file need to have the same name). Now you have to go to the "Template" column where there is the reference to the report file already uploaded but you don't have to click on the link that is displayed you have to click near the link in order to place the cursor on the field then you will be able to see the Multi Value Grup icon .. you click on it and you will be able to upload a new file.
We have tested this process today, however it is not effective in replacing the old version of the report.
After carrying out this process (including related steps from bookshelf - ie "click upload files"), we can generate the report from the relevant siebel view and the previous version of the report is still generated.
Is there a standard process for replacing an existing report that is effective?
Thanks.

Hi ,
This currently seems like a bug , we have encountered this too.
work around is you have to delete the rtf files from server Siebel\client\temp\XMLP directory and upload them again so that they are not cached any more.
same on dedicated client you may have to delete relavant files form siebel\client\temp\xmlp directory and upload again.
Thanks,
Vamsi

WebDynpro error while implementing business package for hr administrator

Hi,
   I am implementing Business package for Hr administrative services in EP 7.0. When I click the iview Start processess I get the following dynpro error. Please do help me as to how should I trace back the problem.   com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.sap.pa.asr.procst.model.procst.types.Asr_Withoutee could not be loaded: com.sap.dictionary.runtime.DdException: Type com.sap.pa.asr.procst.model.procst.types.Asr_Withoutee does not exist
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
     at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:670)
     at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:233)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:654)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
     at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:429)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:932)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:176)
     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:142)
     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:134)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$ComponentUsageManager.createBLCComponentUsage(FPMComponent.java:840)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:1020)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:979)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1230)
     at com.sap.pa.asr.procst.vac.vinit.VInitComp.onInit(VInitComp.java:200)
     at com.sap.pa.asr.procst.vac.vinit.wdp.InternalVInitComp.onInit(InternalVInitComp.java:153)
     at com.sap.pa.asr.procst.vac.vinit.VInitCompInterface.onInit(VInitCompInterface.java:161)
     at com.sap.pa.asr.procst.vac.vinit.wdp.InternalVInitCompInterface.onInit(InternalVInitCompInterface.java:144)
     at com.sap.pa.asr.procst.vac.vinit.wdp.InternalVInitCompInterface$External.onInit(InternalVInitCompInterface.java:220)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:614)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:474)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:218)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:429)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:357)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:670)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:267)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:726)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:662)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:228)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
     at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:808)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:227)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1240)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:340)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:538)
     at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:177)
     at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:429)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:357)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:670)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:267)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:706)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:660)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:228)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.dictionary.runtime.DdException: Type com.sap.pa.asr.procst.model.procst.types.Asr_Withoutee does not exist
     at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
     at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:586)
     at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:286)
     at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:95)
     at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
     at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
     ... 75 more
Please do let me know if anybody could help.
Regards,
Ramesh

Maybe the user used for RFC connection either does not exist or is not granted access to the model data.
Best Regards,
Martin

Setup Bank Statement Processing for Belgium

Hi,
I need help with the setup of Bank Statement Processing for a Belgian system in version 8.8 (pl 16). This is an upgrade from 2005A.
We installed the BTHF add-on and weu2019ve checked u201CInstall Bank Statement Processingu201D in the company details.
Banks and house banks (2 banks) are set up according to the Belgian values to validate bank account data.
However when I go to u201CBank Statement Processingu201D and select Country u201CBelgiumu201D I donu2019t see (let alone can select) the house banks that I set up.
It almost seems like thereu2019s another table that needs to be adjusted, but I have no clue where that could be.
Any ideas?
Thanks,
Josephine

Hi Josephine Noah ,
Try this .... May it will help you...
Steps to Reconciliation Bank Statement
1) Select Review & Install Bank Statement Processing form to detail in business.
2) Fill the informaion bank on the same window.
3.After the need BTHF installed add-on add-on window management for the activation of the Import option on the bank statement process form (in banking module.
4.Need to FD (Definination format) install of the same form by using this add-on, we make banking format (Indian Bank in the SAP format.
Made using this format, then it should assign bank account level house.
Administration> Settings> banking> bank account and select the column (import file
Name), then new window will appear from this window we can create new file formate filled by relavent info (format name (SAP_TEST), make formate-type (account statement) to).
Then assign file format (. BFP), from another add-on
(FormatDefination).
Click on the row that was added as a file format name
After selecting the correct file name to update the file format setup form
Here we show format to bank account
For mapping based on the number of: -
Now make this internal code that is used with external code link (which by bank provided) This code is the date the statement summery you use this code also recognize that the nature of the booking process at the time the bank statement processing (ie BP from used / to the account, property account from / to bank, interim account from / to bank account etc.)
Administration> Settings> Banking> Bank Statement Process> Internal Bank operation code
Administration> Settings> Banking> Bank Statement Process> External Bank Operation Code
Banking> Bank Statement Reconciliation and external> Process statement form (if we're to import from a file, click here button, then select statement we file for processing)
After successfuly import the bank statement file, it shows as a draft.
If we account statement finilize then double-click on the same line to design, then new window opens
If we import into SAP bank statement, if any open party invoive either A / P or A / R should reflect it to produce incoming and outgoing payments. Have assigned its totally dependent on what kind of accounting method users.
Then customize SAP users or to reconcile all bank transaction. When the user double-clicks on row then new windows to open again for the setting.
Thanks
Manvendra Singh Niranjan

Need of Methodology for Netweaver Administrator

Hi frnd
I have a requirement of the Methodology for Netweaver Administrator that means regarding setup, maintenance and support. So frnd if you have plz so me the way for it. If i could get the ppt, i would be more thanful to you all.
Thnx
Adhir

Hey Adhir,
Whole of SAP Managed services follows IT infrastructure Library based approach for this.
There are set of processes like Incident Management, Problem management, Escalation Management,maintaining CMDB and Change management processes.
If you need more on this you can contact me through email.
Thanks & Regards
Vivek

Memory-Based Snapshot Main Process for Transportation Planning getting erro

Hi All,
I have created a Plan in Transportation Planning module and asigned a facility to that plan then i did launch plan, then the program 'Launch Transportation Planning Process' running successfully but with that program Memory-Based Snapshot Main Process for Transportation Planning running and error outing.
the completion text is:
The executable file /u04/NRVIS/apps/apps_st/appl/mst/12.0.0/bin/MSTSNWRK for this concurrent program cannot be executed.
Contact your system administrator or support representative.
Verify that the execution path to the executable file
i have verified the path but there is only have '/u04/NRVIS/apps/apps_st/appl/mst/12.0.0' but no /bin/MSTSNWRK file
can anyone tell me what has to be there actually, is MSTSNWRK file missed?
thanks
vijay

Thanks for your suggestions. I finally able to resolve this issue.
- I'd relink all MSC and MSO exe files. No error found. Still not unable to launch Memory-Based Snapshot.
- I'd turned on all possible debug, trace, etc to see any possible reasons for the failure. But no help at all.
I almost created a TAR (which will need to run numerous useless checkings, talking to some clueless people, and waiting for weeks for doing nothing) and I found out I forgot to check one place - Windows Event Log. Bingo - I found the error and it's because of DLL unmatched (typical Microsoft DLL hell issue).
Using Dependent Walker to see the linking of the MSC exe file, and then I pinpointed which version of MS C++ libraries were missed. Installed the latest MS VS2005 and 2008 redistributable libraries, relinked MSC exe files again, and FINALLY it's fixed.
I need to talk to the DBA who prepare this clone to me....
Edited by: 960630 on Sep 24, 2012 1:01 AM

Multiple processes for a host instance on one server

Hi,
One of the prod environment server memory utilization is getting very high every few days. I searched a bit and found that there are many processes for "BTSNTSvc64.exe" in the task manager. Whenever we restart the host instance a new process is
getting created and the previous process is not getting killed.
This caused multiple processes in task manager and every process is occupying some memory. The process is actually not active but it is creating some bad sectors which is causing the Memory utlization to become high.
I am not able to kill the zombie processes either from Task manager. Server reboot is the option but wanted to know a permanent fix.
Can you please tell me the reason as to why this is happening and also the solution?

How many BizTalk Hosts do you have defined on the system? If you have multiple Hosts defined then you're likely to see one host instance associated with each of the hosts. Each host instance is a service and in the "Task Manager" - Processes you will
see multiple BTSNTSvc64.exe OR BTSNTSvc.exe * 32. This is OK is you have multiple host instances defined on your system (Services MMC will show you BizTalk Service BizTalk Group : BizTalk Host) and BizTalk Administration Console ->BizTalk Group ->Platform
Settings -> Host Instances will also show you the different host instances. Each instance is a multi threaded process running different aspects of the BizTalk Framework/Components. So each process will occupy memory if it is "started". All this is normal
behavior. If you're facing performance issues, you might want to ask the solution designer on their rationale for the number of hosts instances.
So when you stop the service, it does not stop? goes into a non-responsive state? and creates another instance?
Regards.

Need step by step process for creating remote cube

Hi,
I already have a cube from business content, getting data from an ODS, which gets data from the info source,
However we need to model a remote cube in the similar line, that is create the remote cube from the infor source above.
I need a step by step process for creating a remore cube,
Thanks for your help in advance,
Arunava

hi
check this link
Creating a SAP RemoteCube
Prerequisites
·        Direct access must be permitted for the DataSource (in the DataSource maintenance).
·        This DataSource from the sources system was assigned to the InfoSource.
·        You must have defined and activated the transfer rules for this combination. Note the peculiarities of transfer routines:
¡        You need to explicitly select the fields of the transfer structure that you want to use in the routine. See also Creating Transfer Routines.
¡        If you have created a transfer routine, you can create an Inversion Routine for performance optimization.
¡        If you use a formula then the selections in this field cannot be transferred. We recommend using a transfer routine instead.
·        In BW, a source system ID was created for the source system To do this choose Tools ® Assignment of Source System to Source System ID in the main menu.
Procedure
       1.      Choose the InfoSource tree or InfoProvider tree in the Administrator Workbench under Modeling.
       2.      In the context menu, choose Create InfoCube.
       3.      Select SAP RemoteCube as InfoCube type and enter your InfoSource.
       4.      You can define if a unique source system is assigned to the InfoCube using an indicator. Otherwise you must select the source system in the relevant query. In this case the characteristic (0LOGSYS) is added to the InfoCube definition.
See also Characteristic Compounding with Source System ID.
       5.      In the next screen you can check the defined SAP RemoteCube and adjust it if necessary before activation.
       6.      You can then assign source systems to the SAP RemoteCube. To do this, choose Assign Source System from the context menu in your SAP RemoteCube. In the dialog box that follows, choose one or several source systems and select Save Assignments.
The source system assignments are local to the system and are not transported.
Result
The SAP RemoteCube can be used in reporting in cases where it does not differ from other InfoProviders.

Hiring Process for US - BP for HR Administrator

Similar Messages

Maybe you are looking for