PPPI - Process Management - activating standard settings from SAP

System data ECC 5.0
I am trying to use process message category PI_ORDCO. The destination is not assigned. I think the destination should be PI14. PI14 is not listed in the dropdown list.
My guess is the system does not have the current standard settings from SAP "activated". Please help with activating SAP predefined destinations, characteristics, categories, instructions, etc.
Thanks.
(moved by to what I hope is the appropriate forum to get an answer to this)
Message was edited by: Marilyn Pratt

Hi
Please try this ->
http://help.sap.com/saphelp_srm50/helpdata/en/56/54f137a5e6740ae10000009b38f8cf/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/bb/6c0e3b02616a42e10000000a11402f/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/62/fb7d3cb7f58910e10000000a114084/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/5e/88ef3bc8821d0de10000000a114084/frameset.htm
Regards
- Atul

Similar Messages

Process Management for Standard Target Version

Hi All,
I am newbie to hyperion, I am entering values at parent level by taking version type as "Standard Target", Is this possible to create Process Management for "Standard Target" versions? if yes how? Plz help me.
Regards,
Naresh R

I take it you are talking about planning, process management is for "Bottom Up Versions"
From the docs
"Target versions use top-down budgeting. *Manage Process Tasks are not allowed*, and children of target members must be blank (for example, #MISSING) to enable data input at the top level."
Cheers
John
http://john-goodwin.blogspot.com/

Activating standard queries from BI content

Hi Guys,
Can u give me the step by step process to activate standard queries from the BI content with all its related objects.
Thanks in advance...

Hi,
To install Query:
RSA1->Business Content->first choose 'Collection Mode' Start Manual Collection.
Click 'Source System Assignment' button and tick R/3 source system or other source system related (Normally this setup will be done if someone already installed business contents before).
Then left window choose 'Object Type' -> middle window choose 'Query Elements->Query' and double click 'Select Object' -> find the Query you want to install, and click 'Transfer'.
Query will be transferred to right window, click Grouping and choose option 'Only Necessary Objects',
After objects collection is done, click 'Install'-> Install (you can do simulation here, check the help for details).
Thanks & Regards,
SD

Business Process Management use cases within an SAP Environment

Check out the [BPM use case wiki |http://wiki.sdn.sap.com/wiki/display/BPX/BusinessProcessManagementUseCases]to learn how many SAP customers are profoundly transforming their companies by leveraging the discipline of Business Process Management to optimize, monitor, and measure their business operations. Join us as we survey over 20 industry and cross-industry use cases where BPM methodologies and tools were applied to help align business goals with IT implementation to rapidly achieve measurable business improvements. See how other companies got started with BPM and get ideas of how you can begin delivering business value rapidly with a BPM approach in your own company.
Become part of this effort by providing your feedback in this forum or adding your insight and help grow the knowledge base by becoming a contributor the BPM use case wiki by sending a request to the wiki owners.

Hi,
Thanks a Ton for the info. Just to let you know that the link has been changed...
Here is the new link...
http://wiki.sdn.sap.com/wiki/display/BPMUC/BusinessProcessManagementUseCases
Regards,
SrinivaS

How to transport a standard datasource from sap to biw?

hi friends,
I have one standard Datasource which is extracting data from a function module.
But if we see that Data source thr RSO2 then ,there a msg comes with 'Extraction from function module' with some name.
and i saw that function module separately thr se37.
but in RSO2 , i din find that function module name in this Datasource.
so anybody pls tell me how this datasource works and what can i do if i want to transport this data source to BIW?
pls help me out...

Hi Manisha,
You posted this under an ABAP forum, you should have posted it under a BI-forum.
You don't transport from SAP to BI, you just replicate from within BI. (ask you BI consultant).
regards, André

IDOC settings from sap r/3 to sap pi7.3

Hi Guru,
actual problem when i am triggering the idoc from ERP,it is trigeering to the abap stack in sap pi.but i am using idoc_aae adapter at sender side,the message is flowing from sap ERP to file but the message is seen in sxmb_moni,but actually it is not seen in moni .
Please if any one have the idoc setting from sap erp to sap pi7.3. and iam using ICO configuration.
Please help me
Regards
Reddy

Hi,
Please go through the below link :
http://wiki.sdn.sap.com/wiki/display/XI/ALE-Idocconfiguration-+%28R3XIFile%29
Also in your software component version please check whether import of IDocs and RFCs are allowed
from your respective ECC system, and check the ECC system parameters are correctlt maintained or not.
Try out once.

PING Process :: Checking App System availability from SAP R/3

Hi
Our requirement is to check Whether Application System is UP or DOWN before sending the data from SAP Server like Pinging the application system from SAP System.
We are using the Web Service as Target Application System & SAP R/3 as Source System now SAP R/3 will call one RFC ( like Z_Ping ) before calling any other RFC to send data to WebService. Following is the configuration -->
SAP R/3 -- Sender RFC Adapter -- SAP XI -- Rec SOAP Adapter -- App System ( Web Service )
Now can you tell me what is the appropraite way to do this, because in case of System Error ( in case when WebService is down or Server on which WS is installed is down ) XI is not receving any exception payload so no mapping is happening.
Though I created the " Error " xsd & used it as a Fault message but the mapping is not getting initiated.
Can you tell me how I can achieve this & suggest me the design specification.
Best Regards
- Lalit -

hey
u can do this using alerts,configure alerts so that it gets triggered whenever anythin wrong happens with Z_ping.and if response is negative then dont send subsequent messages.
alerts will always work irrespective of mapping.
but one thing is that triggering/not-triggering the subsequent message will be manual coz u need to check the alert before u send messages
thanx
ahmad
Message was edited by:
Ahmad

Upgrading to Oracle BPEL Process manager 10.1.3 from 10.1.2

Hi,
In our project, we are currently using Oracle BPEL Process Manager 10.1.2 over Oracle Enterprise Server 10.1.2.
Now we want to upgrade both BPEL Process manager to 10.1.3. I am very much confused what of version Oracle BPEL process manager is compatible with Oracle Enterprise Server. In the downloads page of Oracle I can find Oracle BPEL process manager 10.1.3.3 for other applications like WebLogic, Jboss and Websphere but not for Oracle Enterprise server 10.1.3.3
I am able to find Oracle BPEL process manager 10.1.3.1 in the download page.
Can somebody tell what version of BPEL Process manager and Oracle Eneterprise server I need to download such that I can run my bpels developed in 10.1.2 without any problems in 10.1.3
Please send some input on this.
Thanks,
-Vidya

Is that Oracle Enterprise Server or Oracle Application Server? If it Application server, You can install Oracle SOA Suite 10g 10.1.3.1 and install Patch 10.1.3.3 to become 10.1.3.3

How to automate the process of vendor invoice verificaiton from SAP

My client to scan the Invoice (once it is received from vendor), upload it in SAP, the User will look at the Invoice in SAP and then perform Invoice Verification in MIRO.
The Process mechanics is
1.Plant Manager will receive the Invoice physically by the vendor
2.Plant Manager then will fax the Invoice to a central location/Team
3.It gets scanned and gets uploaded in SAP
4.The Manager/FI folks will looked at this scanned copy and then perform
Inv. Verification.
After this i need to enhance the MIRO screen so that once PO or GR no will be entered,
then corresponding vendor invoice has to be displayed in same screen
Kindly can u give me approach to for the above requirement.
Thanks n regards,
Manjunath
Moderator message: "spec dumping", please work yourself first on your requirement.
Edited by: Thomas Zloch on Nov 22, 2011 12:12 PM

any input...........

Active Directory cn field not updated from sap HR using ldap.

Hi,
Apologies if this is in the wrong forum area.
I am using the LDAP facility to create and modify Active Directory records from sap HR. Initially, the name field cn that was coming across into AD was in the format of the logical system and employee number, eg, RD4CLNT22000000711.
I then implemented the BADI HRLDAP_ATTRIBUTES which then changed this name field cn in the active directory listing to the format; surname, forename.
It works fine when I create a new user, however the problem comes when I update the persons name in the sap hr module. The data that comes across into Active Directory shows the change to the persons surname sn, forename and displayname fields is there but the cn field is still showing as the previous name.
In short, when a new user is created, the cn field in active directory is correct
(surname, forename) but when the employees name is modified, that change is not brought across to the cn field even though the surname, forename and displayname fields are updated correctlyon AD.
We are on release 4.70.
Anyway, if anyone could help I would be very grateful.
Thanks
David

Hi
The problem it is causing us is that the cn field is incorrect and does not mirror the change in sap HR, therefore the Active Directory entry for the employee is not totally accurate.
When an employee changes their name in SAP HR - usually their surname, we would then want to update the employees active directory account to show this change and this includes the cn field also. At the moment the firstname, lastname fields do get updated with the change so we would want the cn field to show this as well otherwise the cn field would be incorrect and not match up with the employee's AD firstname & lastname fields.
Dave

Project Profile from SAP-PS in cProjects

Hi,
Need your suggesttion on the below issue. We have cProject & R/3 integration. Project structure will be created in cProjects which will also create a project in SAP-PS. As per standard SAP-PS, CPR0001 is project profile to be used for cProjects & PS interface. Project profile (CPR0001) contains standard settings of SAP such as controllig area / company code / plant etc. I had copied CPR0001 project profile & created new profile to be used for creating project as per our organsaition structure. I observed while creating project from cProjects, it is considering CPR0001 project profile & accordingly the organisation structure is copying where as our required project profile is different.
I would like to request in cProjects, where it is calling project profile & to make the project profile as per our requirments.
Thank you for your cooeparation.
Regards,
Ranjan

Hi Ranjan,
1. Project element is creating as WBSE & project definition in PS. But there is no one -to-one mapping. I would like to transfer various phases as WBSE in R/3 but it is n't happening
>> There tow scenario of the replication, one is role-based, other is task-based. In case of role-based, the phases are not used, as role is not under the phase. In case of task-based, the phase should be used, as it is in most cases the parent of the task. I am not 100 percent sure at this point.
2. Dates are n't getting transferred to project in project structure of SAP-PS.
>> At the replication, only some data are mapped to the WBS, mostly the costs relevant information, as the purpose of this functionality is costs. Even the left-right relationships can not guaranteed in some cases.
3. The WBSE which created in PS from cProjects, master data are locked
>> Worked as designed. The idea is to forbid the use change the master data of the replicated WBS. It is somehow inflexible, but it is customer requirement, which trigger this feature. You can unlock it manually in the ERP system.
4. Tasks are n't getting transferred as network activity into PS
>> Not possible in cPro. 4.0, in release 4.0 the project system integration (other name multiple level controlling) will be mapped to WBS. In Release 3.1, it is possible to get. But from my point of view, map to WBS is the better way.

Download Graphics from SAP

Hi,
I am bit curious to know, Is there any standard program or process to download Logos (bitmaps) from SAP into local system.
We have logos in our SAP system. So i would like to download them from SAP into local drive.
Thanks,
Subba.

Hi,
Try FM's from the Function Group GRAP.
Especially the FM's
GRAPH_RECEIVE.
Hope this helps...
Lokesh
Pls. reward appropriate points

Process Management Email

What is the difference between ...
granting a user the role "Receive Email Alerts for Process Management" AND
"Add Alert" from the Security classes permissions screen ?

I wanted to try to test the myself but after I changed the scenario process management setting to A I get a HTTP 500 error when I process manage and don't get any emails. I registered the mailer.dll but that didn't work.
Anyway, I would set up a user with one process level role and then see what email(s) they get. Then add additional process level roles and see if that is what is adding additional emails or not.
Another test you could also try testing with only one security class set for alert and then add additional ones to see what happens.
When you process manage do you only process manage one entity at a time or do you do the Parent and all decendents?
Below shows what the 9.3.1 Security Admin Guide says this is who is notified at what level but it does not say what happens if a user has more than one role.
Process Unit Level
Before or After Action Process Management User Roles Notified
First Pass Users with ALL or PROMOTE access to the entity are notified.
Review Level 1 Reviewer 1 and Submitter roles are notified.
Review Level 2 Reviewer 2 and Submitter roles are notified.
Review Level 3 Reviewer 3 and Submitter roles are notified.
Review Level 4 Reviewer 4 and Submitter roles are notified.
Review Level 5 Reviewer 5 and Submitter roles are notified.
Review Level 6 Reviewer 6 and Submitter roles are notified.
Review Level 7 Reviewer 7 and Submitter roles are notified.
Review Level 8 Reviewer 8 and Submitter roles are notified.
Review Level 9 Reviewer 9 and Submitter roles are notified.
Review Level 10 Reviewer 10 and Submitter roles are notified.
Submitted Review Supervisor role is notified. Only users with this role can approve
*the submitted process unit.
Approved Reviewer 1 to Reviewer 10 and Submitter roles are notified.
Published Users with ALL, READ, or PROMOTE access to the entity are notified.
Edited by: user2609991 on Aug 13, 2009 4:50 AM

Does SAP Provide any standard conversion program for Batch Managment activa

Hi,
An idea if SAP Provides any standard program to conversion of non batch managed material to batch managed material in a productive SAP Environment and close open documents,
It would be great help if somebody can reply to these queries.
Thanks in advance
Regards
Bijaya Pradhan

Hi
Use the same Driver program RIPROV00 which is used as Script driver program to fire the output from smartforms also
Only thing is little bit you have to modify the program such that it triggers the smartform instead of Script.
I think there is no smartform driver program for this IW21.
see some standard SF driver program like RLE_DELNOTE and
modify it and use it.
Reward points for useful Answers
Regards
Anji

What are the major process to transfer the data from legacy to sap system.

What are the major process to transfer the data from legacy to sap system using BDC at Real Time only?

hi,
BATCH DATA COMMUNICATION
main methods are:
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a data transfer program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
The transaction code, if you do not already know it.
Which fields require input i.e., mandatory.
Which fields can you allow to default to standard values.
The names, types, and lengths of the fields that are used by a transaction.
Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System Status.)
Step through the transaction, entering the data will be required for processing your batch input data.
On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
Display these by choosing System Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which youll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
Create a BDCDATA structure
Write the structure out to a session or process it with CALL TRANSACTION USING; and then
Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
Data that is entered into screen fields.
Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
DYNPRO: Screen Number. Set this field only in the first record for the screen.
DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to (blank) for all other records.)
FNAM: Field Name. The FNAM field is not case-sensitive.
FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
User Name: User name
Group: Name of the session
Lock Date: The date on which you want to process the session.
Keep: This parameter is passed as X when you want to retain session after
processing it or to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
Tcode: Transaction Name
Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter 1 is transaction code.
Parameter 2 is name of BDCTAB table.
Parameter 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
About Direct Input
In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
You can start a Direct Input program in two ways;
Start the program directly
This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
Starting the program via the DI administration transaction
This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
- Create variant
- Define job
- Start job
- Restart job
Common batch input errors
- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
- The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
- On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
- The BDCDATA structure contains fields, which are longer than the actual definition.
- Authorization problems.
RECORDING A BATCH INPUT
A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
You can either use SHDB transaction for recording or
SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
And from here click recording.
Enter name for the recording.
(Dates are optional)
Click recording.
Enter transaction code.
Enter.
Click Save button.
You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
Click Get Transaction.
Return to BI.
Click overview.
Position the cursor on the just recorded entry and click generate program.
Enter program name.
Click enter
The program is generated for the particular transaction.
BACKGROUND PROCESSING
Need for Background processing
When a large volume of data is involved, usually all batch inputs are done in background.
The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
There are several reasons to submit programs for background execution.
The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
You can use the system while your program is executing.
This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
The transaction for background processing is SM36.
Or
Tools ? Administration ? Jobs ? Define jobs
Or
System ? services ? Jobs
Components of the background jobs
A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
Job class. Indicates the type of background processing priority assigned to the job.
The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
Job steps. Parameters to be passed for this screen are as follows:
Program name.
Variant if it is report program
Start criteria for the job: Option available for this are as follows:
Immediate - allows you to start a job immediately.
Date/Time - allows you to start a job at a specific name.
After job - you can start a job after a particular job.
After event - allows you to start a job after a particular event.
At operation mode - allows you to start a job when the system switches to a particular operation mode.
Defining Background jobs
It is two step process: Firstly, you define the job and then release it.
When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
HANDLING OF POP UP SCREEN IN BDC
Many times in transaction pop up screen appears and for this screen you dont pass any record but some indication to system telling it to proceed further. For example: The following screen
To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
BDC_CURSOR is also used to place cursor on particular field.
A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
Prerequisite to write this BDC interface as indicated earlier is:
1. To find screen number
2. To find screen field names, type of the field and length of the field.
3. To find BDC_OKCODE for each screen
4. Create flat file.
generally Batch Input usually are used to transfer large amount of data. For example you are implementing a new SAP project, and of course you will need some data transfer from legacy system to SAP system.
CALL TRANSACTION is used especially for integration actions between two SAP systems or between different modules. Users sometimes wish to do something like that click a button or an item then SAP would inserts or changes data automatically. Here CALL TRANSACTION should be considered.
2. Transfer data for multiple transactions usually the Batch Input method is used.
check these sites for step by step process:
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
null

PPPI - Process Management - activating standard settings from SAP

Similar Messages

Maybe you are looking for