Transfer billing data from CRM to FI, function module ALE_ACC_BILLING_POST

Hi ABAPers,
we have a scenario were we want to post billing documents from a custom developed application running on a CRM system into FI.
My idea is to call the function module ALE_ACC_BILLING_POST to create an outbound IDoc in the CRM and send it to the ERP system.
I guess, this should not be a problem. I'm just not sure because of one import parameter of the mentioned function module: CUSTOMERCPD. Does anybody know if I have to fill this parameter? Does it mean that the function module can only be used for so called CPD customers (one time customers) in FI?
Thanks in advance and best regards,
Martin

Dear Colleague,
You have different method to send parameters to Workflow.
1. Method
Container Set Element
DEFINE SWC_SET_ELEMENT.
CALL FUNCTION 'SWC_ELEMENT_SET'
    EXPORTING
      ELEMENT   = &2
      FIELD     = &3
    TABLES
      CONTAINER = &1
    EXCEPTIONS
      OTHERS    = 1.
END-OF-DEFINITION.
Set the data into Workflow container
    SWC_SET_ELEMENT IT_CONTAINER 'parameter1' lv_parameter1.
Start the Workflow
    CALL FUNCTION 'EWW_WORKFLOW_START'
      EXPORTING
        X_TASK          = 'WS90000001'   " your wf
      IMPORTING
        Y_WORKFLOW_ID   = WF_ID " your workitem id
      TABLES
        X_CONTAINER     = IT_CONTAINER
      EXCEPTIONS
        INVALID_TASK    = 1
        NO_ACTIVE_PLVAR = 2
        START_FAILED    = 3
        GENERAL_ERROR   = 4
        OTHERS          = 5.
2. Method,
You can also add your parameters direly to a container,
DATA: lt_simple_container TYPE TABLE OF swr_cont,
        ls_simple_container TYPE swr_cont.
ls_simple_container-element = 'parameter1'.
ls_simple_container-value = lv_parameter1.
APPEND ls_simple_container TO lt_simple_container.
CALL FUNCTION 'SAP_WAPI_WRITE_CONTAINER'
    EXPORTING
      workitem_id      = WF_ID " your workitem id
      do_commit        = 'X'
    TABLES
      simple_container = lt_simple_container.
Bulent.

Similar Messages

How to extract data from generic view and function module

hi experts,
can anybody give me the steps to extract data from generic view and functon modules.
thanks and regards
venkat

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0f46157-e1c4-2910-27aa-e3f4a9c8df33
https://websmp103.sap-ag.de/~sapidb/011000358700007535452002
Hope it Helps
Chetan
@CP..

Importing master data from R/3 through functional modules

I am facing the below error when I try to import master data from R/3 through the inbound functional module /DMF/MDIF_PRODUCT_INBOUND to the PMR component (PMR - Promotion Management for Retail).
"Runtime error CALL_FUNCTION_NOT_FOUND has occurred"
Landscape - I have RTLDMF 1.1 and RTLPROMO 7.0 installed on top of Netweaver with EHP1 in a server which also has BI system. While the R/3 is present in another system.
Appreciate any help. Thanks!

Hi Khan,
You can create your own datasource source, by Tcode RSA2. In this link you find more information:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/28/4c553c42360a40e10000000a114084/content.htm
Also please check this link, that provides the steps to create/maintain the generic datasource:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/content.htm
I hope it contributes.
Regards,
Sinara Moraes

Extract data from CRM to SAP R/3

Hi Experts,
I Facing Problem to Extract the data from database table BUT000 in CRM 2.0 System to SAP R/3 whether its possible to update the data directly in R/3 system from CRM. whether any functional module exists?
Plz Provide me details about it

Why do you need to copy it? The data is easily available from R/3 via RFC.
Rob

Transfer of Business Partner Master data from CRM to TIBCO.

Hi All,
We intend to integrate CRM4.0 with TIBCO for transfer of Business Partner Master data from CRM to TIBCO.
Can anyone provide solution for the same. One of the think is through XI.Please correct if it is the right way to do it?.
Also, would appreciate if someone can provide documentation or links for integration.
Regards,
Mehul Shah.

Hi Rahul,
Yes you can integrate CRM and TIBCO using XI.
Check the below links
transfer the Business Partners from the CRM system to XI and to MDM.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/406efa7e-388a-2910-f9b8-81913b0ca57f
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50260ae5-5589-2910-4791-fc091d9bf797
any XI content delivered by SAP can be found in the SAP service marketplace which you can enter http://www.sap.com/services/bysubject/servsuptech/index.epx.
a) After you entered the service marketplace go to Software Download under the header SAP Support Portal.
b) Next navigate to Download -> Support Packages and Patches -> Entry by Application Group
c) In the main window select SAP Content and then Process Integration Content (XI Content).
d) Now you should see a list of XI content packages.
The package containing XI content for CRM is
XI CONTENT BBPCRM
In addition you find some packages that offer mappings from CRM interfaces to industry standards like RosettaNet or STAR standard, like
XI CONTENT ROSETTANET CRM
XI CONTENT STAR CRM
Some of these packages may require a license, therefore I am not sure if they are visible to you.
As per my knowledge, XI has CRM pre-delivered content and usually it communicates thru Proxies,Http, RFCs..
And in your scenario , you can always go for Proxy communication
Have a look into these threads
CRM and SAP XI
SAP CRM integration with XI
How to access the pre-delivered XI Integration Content for APO ,SCM or CRM
Dont forget to Reward points if this helps
Regards
Pragathi.

Stages when pulling data from CRM datasource?

Hi,
We are pulling data from CRM.Please explain me the steps while pulling data from CRM.

Hi,
Data from CRM to BW is divided into diiferant Data sources.
First need to find data source name.
Use the following seps
First of all, activate the CRM DSs by scenario:
1) Activate the application component hierarchy (tcode RSA9). Changes made to the application component hierarchy in the CRM system can be transferred to the BW using the "Edit Application Component Hierarchy" (SBIW - Postprocessing of DataSources).
SAP Note 434886 must be implemented in CRM 3.0 before the application component hierarchy is activated.
2) Activate the Business Content DataSources (tcode RSA5).
Select/enter the application component and choose Execute (F8).
To compare the shipped and active versions, choose the 'Select Delta' pushbutton. If there is no active version of the DataSource, it is selected automatically.
To activate the shipped version, choose the 'Transfer DataSources' pushbutton.
3) Management of the versions of the BW-Adapter metadata (tcode BWA5). All DataSources are displayed that are managed by the BW Adapter.
As in transaction RSA5 (Service API Metadata Activation), the 'Select Delta' function can be used to select the inactive DataSources or compare shipped and active versions.
You can also go directly to the screen for maintaining DataSources that are managed by the BW Adapter.
The 'Compare Version' function makes a detailed comparison of the shipped and active versions.
All BW-Adapter metadata is considered when versions are compared:
Header information (Table SMOXHEAD)
Mapping information (Table SMOXRELP)
Global selection conditions (Table SMOXGSEL)
Attribute key fields (Table SMOXAFLD)
It is depends if you want to use in BW some ready made (Business Content) data analysis models.If so, you need to find your data source in RSA5 in CRM and activate it. See this link http://help.sap.com/saphelp_nw2004s/helpdata/en/04/47a46e4e81ab4281bfb3bbd14825ca/frameset.htm to find Cube you want to analyze in BW, and Data Source connected to it.
BW CRM analysis.
http://help.sap.com/bp_biv135/html/bw.htm
CRM Extraction
Pls chk this link for Crm enhancement
Enhance standard data sources in CRM
BWA1 is for all standard crm datsource maintaince
rsa2 for generic datasource
BWA5 i think we use this Tcode after RSA5 activation additionally.
yes(incase of delta)
BWA7 do we have to use this tcode along with BWA1 for standard datasources also or else only for generic datasource.
irrespective of the type of dtasource,use it if you want to load delta(you need to delta enable the datasource here)
So we don't need to put the code as we traditionally do it for R/3 , if we just mapp the fields that would bring the data for these fields.
as i told in CRM we willwrite code in BADI in case you have done enhancement
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/a-c/customer%20enhancements%20and%20userexits%20in%20bw%20-%20sap%20netweaver%20%20know-how%20network%20webinar.pdf
also chk this(credit goes to the writer)
CRm enhancement:
1. Enhance Extract Structure with the required fields. (Create & include an append structure to the extract structure via transaction RSA6).
2.a) Release the fields of the append for usage. ( To do this, double click on the Datasource and remove the flags in the column 'Hide Field' for all fields of Append).
2.b) If the new fields cannot be seen in the extract structure of the transaction BWA1 then change and save the datasource, and then activate it in RSA6.
3. Define your mappings in BADI (CRM_BWA_MFLOW) to fill these fields.
Goto SPRO . Follow the path ->SAP Implementation guide ->Implementation with other mySAP components ->Data transfer to the Business Information Warehouse-> Settings for the application specific datasources (CRM)->Settings for BW adapter-> Badi :BW adapter :Enhancement of datasources in messaging flow.
4. Replicate the new Datasource to BW.
5. Expand the Communication Structure in BW.
6. Maintain transfer Rules for the new Datasource.
7. Activate the trasfer rules and perform the upload.
Refer to the SAP Note 692195 for more info ......
pls Check this links..
regarding bw crm extraction
http://help.sap.com/bp_biv235/BI_EN/html/BW/CRMAnalytics.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/be/92fb3b28904f73e10000000a114084/frameset.htm
CRM extraction
Hope this helps,
Regards
CSM Reddy

Problem with upload data from CRM to BI system

When I try to perform full upload data from CRM to BI system with data source 0BPARTNER_ATTR (active version: Excutable). I waited for a long time but there are not any records were transfered (total records need to upload are 130) . I checked the log and can't find any errors.
Pls help me solve this problem.
Thanks and regard

Hi,
on the next day, the process finished with status not success.
The detail errors is:
Extraction(messages): Missing messages
          Missing message: Request received
          Missing message: Number of sent records
          Missing message: Selection completed
Transfer (IDocs and TRFC): Errors occurred
          Data package 1: arrived in BW; Processing: Selected number does not agree with transferred n
          Request IDoc: Application document posted
          Info IDoc 2: sent, not arrived; Data passed to port OK
          Info IDoc 1: sent, not arrived; Data passed to port OK
          Info IDoc 3: sent, not arrived; Data passed to port OK
          Info IDoc 4: sent, not arrived; Data passed to port OK
However, the data has been uploaded to infoobject. Pls explain to me about this error and why the data can be uploaded with this error.
Regard

Error while extracting data from CRM

Dear all,
I have used some standard and generic datasources to extract data from CRM. These were working fine for more than a year and are scheduled in Process chains. For the past few days I am getting Caller 09 error as shown below, only for the generic datasources. I have checked the connection,replicated the datasources and activated them, reinitialized and have tried all the solutions that were posted earlier, but still the process chain fails. When I execute the process chain for generic datasources manually, it is working fine.
When I tried in RSA3 for both standard and generic datasources in CRM with update mode D, I get a message 'Error occured during the extraction',
Kindly suggest what can be the problem.
Error message from the source system
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
Thanks all in advance.
Regards
Adhira Anand

Hi Meyappan,
I have checked SM37, SM21 and ST22. There are no errors.
in SM37 the below log is displayed.
Job started
Step 001 started (program SBIE0001, variant &0000000005420, user ID ALEREMOTE)
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = ZCRM_SRV_DEFECT
RLOGSYS    = CLNT645BIP
REQUNR     = REQU_4JHQ8HH6KA40JHC1TYLYIV2W2
UPDMODE    = D
LANGUAGES = *
         Current Values for Selected Profile Parameters               *
abap/heap_area_nondia......... 2000000000                              *
abap/heap_area_total.......... 2000000000                              *
abap/heaplimit................ 40000000                                *
zcsa/installed_languages...... DE                                      *
zcsa/system_language.......... E                                       *
ztta/max_memreq_MB............ 2047                                    *
ztta/roll_area................ 6500000                                 *
ztta/roll_extension........... 2000000000                              *
1 LUWs confirmed and 1 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DATA
IDOC: Info IDoc 2, IDoc No. 101415, Duration 00:00:00
IDoc: Start = 13.10.2010 22:51:39, End = 13.10.2010 22:51:39
Synchronized transmission of info IDoc 3 (0 parallel tasks)
IDOC: Info IDoc 3, IDoc No. 101416, Duration 00:00:00
IDoc: Start = 13.10.2010 22:51:42, End = 13.10.2010 22:51:42
Job finished

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

Is there any statement to transfer the data from unix server to another

Hi All,
Is there any statement or function module avaliable in sap to transfer the data from one unix server to another unix server apart from FTP(file transfer protocol).?
My requirement : I need to fetch the data from one unix server to another sap server. i have a option of FTP but i need to transfer the unix data to another server internal table.
I need to move the unix data to another sap sevrver internal table
Regards
Raja

not sure what your exact requirement is, but
if both servers are in the same system group, you could potentially just mount the unix directory from the source machine to the target with nfs mount or something.
if not, you could consider remote function call. create a remotable function module on the source machine to read the data into an internal table, and call that function module from the target machine. this requires creating entries in the RFCDES table (i think via SM59?). on the target machine, you would call function y_whatever destination xyz, where xyz is the RFCDES you set up. it works great.
dave

Migrate Cprojects data from CRM 4.0 to CRM 5.0

Hello,
Please help me with this ?
We have upgraded the CRM 4.0 (cProjects 3.1) to CRM 5.0 and doesnu2019t bring cProjects data new upgraded server (CRM 5.0).we have installed the add-on CPRXRPM in CRM 5.0 and would like to know how to migrate the cProjects data from CRM 4.0 to CRM 5.0
Regards,
SJ

Okay the only question is that is your CRM 40 system and the CRM 2007 separate systems? If so then you can use the XIF IDOC adapter to setup the transfer between the two systems.
Now if the CRM 40 system is being upgraded to CRM 2007 then you don't have to "transfer" data.
As far as the CRM consultant role, you better understand basic IDOC setup and be able to do data mapping between the older and newer version. Luckily you shouldn't have a lot of mapping work as 2007 IDOC structure is a refinement of 4.0.
For more XIF information search the CRM general and framework forum.
Take care,
Stephen

0CRM_SALES_ACT_1 takes a long time to extract data from CRM system

Hi gurus,
I am using the datasource 0CRM_SALES_ACT_1 to extract activities data from CRM side. However, it is taking too long time to get any information there.
I applied the SAP NOTE 829397 (Activity extraction takes a long time: 0crm_sales_act_1) but it did not solve my problem.
Does anybody knows something about that?
Thanks in advance,
Silvio Messias.

Hi Silvio,
I've experienced a similar problem with this extractor. I attempted to Initialize Delta with Data Transfer to no avail. The job ran for 12+ hours and stayed in "yellow" status (0 records extracted). The following steps worked for me:
1. Initialize Delta without Data Transfer
2. Run Delta Update
3. Run Full Update and Indicate Request as Repair Request
Worked like a champ, data load finished in less than 2 minutes.
Hopefully this will help.
Regards.
Jason

I would like to transfer all data from my iPod classic to my new computer with windows 8.1. My old computer's cpu died. Utilizing iTunes which only allows iTunes albums purchased at iTunes store. The cd's were loaded via iTunes originally.

I would like to transfer all data from my iPod classic to my new computer with windows 8.1. My old computer's cpu died. Utilizing iTunes which only allows iTunes albums purchased at iTunes store. The cd's were loaded via iTunes originally.

Install disk drive from old computer in an external enclosure.
Then copy the complete iTunes library from the disk drive to the disk drive in the new computer.

Transfer of data from one iTunes account to another

My son has been using my iTunes account for games. Got him a 5th gen iPod touch. Can I transfer his data from my iTunes acct to a brand new iTunes account ? He is so ovewhelmed that he will lose his data .

Have you looked at the Family sharing program?
http://www.apple.com/ios/whats-new/family-sharing/

HOW TO TRANSFER HISTORICAL DATA FROM ONE ACCOUNT TO ANOTHER

제품 : FIN_GL
작성날짜 : 2006-05-29
HOW TO TRANSFER HISTORICAL DATA FROM ONE ACCOUNT TO ANOTHER
=============================================================
PURPOSE
특정 기간의 Balance 를 Account 별로 Transfer 하는 방법에 대해 알아 보도록 한다.
Explanation
GL 의 Mass Maintenance 기능을 이용하면 한 Account 에서 다른 Account 로 혹은 Multiple Account 에서 다른 하나의 Account 로 Balance 를 이동 시킬 수 있다.
1. GL Responsibility 에서 Other> Mass Maintenance 를 선택한다.
2. Move/Merge 작업을 위한 Request Name 과 Description을 입력한다.
3. Request Type 으로 Move 혹은 Merge 를 선택한다.
4. source-to-target account 를 위해 line number 를 입력한다.
5. LOV 에서 source Account 를 선택하여 입력한다.
모든 Account 는 enable 상태여야 한다.
6. target account 역시 LOV에서 선택하여 입력한다.
7. 지정한 작업을 수행 하기 전에 먼저 확인 작업을 할 수도 있다.
8. 작업한 내용을 저장한다.
9. Move/Merge request 를 수행한다.
Example
N/A
Reference Documents
Note. 146050.1 - How to Transfer Historical Data from One Account to Another

Follow the directions here:
http://support.apple.com/kb/HT2109

Transfer billing data from CRM to FI, function module ALE_ACC_BILLING_POST

Similar Messages

Maybe you are looking for