Meter data aquisition system through SAP

Hi All,
Can anyone tell me the way to implement the MDAS through SAP.
Thanks in advance
Edited by: Godadhar Maity on Apr 8, 2010 7:22 AM

got ans

Similar Messages

What is data archiving and DMS(Data Management System) in SAP

what is data archiving and DMS(Data Management System) in SAP
Welcome to SCN. Before posting questions please search for available information here and in the web. Please also read the Rules of Engagement before further posting.
Edited by: kishan P on Aug 31, 2010 1:06 PM

Hi,
Filtering at the IDoc Level
Identify the filter object (BD59)
Modify the distribution model
Segment Filtering
specify the segments to be filtered (BD56)
The Reduced IDoc Type
Analyze the data.
Reduce the IDoc type (BD53)
Thanks and regards.

Integration Oracle Utilities CC&B w/ non-Oracle bespoke Meter Data Management system

Hello all,
In your opinion, what's the best way to integrate a bespoke (non-Oracle) Meter Data Management system with Oracle CC&B 2.3.1 or 2.4?
I came up with a few possible scenarios and would love to hear your opinion:
1. Use CC&B Meter Read upload (MUP) batch process to upload reads from our bespoke Meter Data system.
2. The bespoke Meter Data Management system adds Meter Reads to CC&B using a CC&B Inbound Service.
3. At Billing time, CC&B invokes a Get Consumption Algorithm (invoked before the Bill Segment Creation Algorithm) which is responsible for requesting the reads from our bespoke Meter Data Management system.
This is the approach used by the Oracle CC&B-Oracle MDM integration when it comes to Usage requests/transactions.
4. Any other idea? Feel free to share.
Thanks

Hello all,
In your opinion, what's the best way to integrate a bespoke (non-Oracle) Meter Data Management system with Oracle CC&B 2.3.1 or 2.4?
I came up with a few possible scenarios and would love to hear your opinion:
1. Use CC&B Meter Read upload (MUP) batch process to upload reads from our bespoke Meter Data system.
2. The bespoke Meter Data Management system adds Meter Reads to CC&B using a CC&B Inbound Service.
3. At Billing time, CC&B invokes a Get Consumption Algorithm (invoked before the Bill Segment Creation Algorithm) which is responsible for requesting the reads from our bespoke Meter Data Management system.
This is the approach used by the Oracle CC&B-Oracle MDM integration when it comes to Usage requests/transactions.
4. Any other idea? Feel free to share.
Thanks

Oracle Meter Data Management Integration with SAP ISU

Hello Everyone,
I am aware of the fact that Oracle has released a Media pack for the subject integration as discussed here and that media pack works only for SAP ERP 6.0 EHP 5 with ISU_AMI_2.
We have got OU MDM Release 2.1 Media Pack v4 and SAP ERP 6.0 EHP 4 with ISU_AMI_1 and hence Adapter in MDM won't help to achieve integration with SAP as our SAP EHP is lower than what is required for the MDM adapter. We have got SAP PI which would help the SAP End in the integration.
What are the possible work-around(s) to achieve the integration between Oracle MDM and SAP ISU without using the Media Pack/Adapter?
How does MDM exposes its services (inbound/outbound) to be consumed/triggered by External systems (i.e. SAP ISU)?
List of Services (inbound/outbound) exposed by Oracle MDM for integration?
Your time and help is much appreciated.
Regards,
Adil Khalil

Did you find the document Oracle Utilities Customer Care and Billing - Meter Data Management Integration Implementation Guide?
I searched on eDelivery and Oracle Support, but cannot find the document.

How to extract meta data of documents from SAP R/3

dear all,
i`am working in aproject where we connect the documents for SAP R/3 applications.we maintain our own repository for that purpose.it may be in bound or out bound according to customer needs.the meata data related to the documents is stored in SAP.our requirement now is to have that metadata available in our repository .can any one guide me how to write ABAP code for extracting meata data from SAP and enable even nonSAP users to have the access for the documents.
thanks in advance
ravi

Hi,
One way to do this is probably set a connection between SAP Database and an external database and store the meta data into external database from where a non-sap user will have an eccess to the data.
Steps required are :
1. we have to involve basis team also in that.
2. they will make one entry
in DBCON table
(that entry will point to secondary database/external database)
(suppose the name of this secondary connection is HRCON)
3. Also they will make connection string
in application server.
4. After that,
we should have
the table definition in SAP dd dictionary
and also
the same defintion
in the external database.
5. now in abap code,
we have to use like this.
DATA: mydbcon(30) TYPE c.
mydbcon = 'HRCON'.
INSERT ydev_msg_cur CONNECTION (mydbcon)
FROM msg_cur .
<b>Hope this helps.
Please mark helpful answer.</b>
Regards,
Amit Mishra

How to telent system through sap router

Dears,
Do you know how to telnet system through saprouter ?
(ex. local pc > saprouter > telnet some system)

Hello
You can use SAPRouter for make a telnet connection between your client and remote host, but ssh is not supported by SAP (OSS note #37001).
Example:
In the saprouttab that use your SAPRouter add the entry:
P <IP adress PC> <IP remote host> 23
You can use SNC Encryption.
Bye

Monitoring/Chekcing the avalability of other system through SAP PI

Hi All,
Is there any mechanism /process, by which we can monitor the availabilitiy of other system through PI.
Other option would manually creating interface to send the probe message and wait for the response,then process the probe message.
Please share your idea/BOKs on this.
Thanks,
MK

Hi,
Few ideas:
1. SAP System: RFC communication channel is recommended and frequent dummy messages can be send to see if it is working.
Note: Monitoring by CCMS of Solution Manager is recommended.
2. Non-SAP System: Use File communication channel for FTP/Ping and monitor communication channel for any issue.
Regards,
Gourav

Sending Data Requests - System Monitoring - SAP Library

To add a comment, please log in or register on the top of this page and choose Reply. Please write your comment in English.
You can also go back to the SAP help page.

Hi!
Here we use IBM ITM SAP agent to do this work.
ITM add some programs and transactions to configure this. We configure RZ20 CCMS monitors and export those alert information to ITM agent that has also integration with IBM Maximo (ITIL based tool to track incidents,changes,problems, etc...)
I don't have any details about coding of this agent but I think you could use a ready-to-use product or develop your own based on your needs.
Maybe using an out of the box product will reduce costs managing code (develop and maintenance)

How can SMART METER Technology be integrated with SAP ISU system?

At present the SMART METER technology is integrated with SAP ISU through a third party vendor. The idocs are sent to a third party and the readings are downloaded and sent back in idoc segments.
How can the integration be done without the third party intervention.

HI
SAP XI needs to be used for 3rd party intervention to send and recive idocs..
or there are some thrid party softwareslike MDUS ,meter data utilisation system.which wil be again a interface between sap and ami system
so basically its like sap syst--sap xi3rd patry 4 ami comapnyami system
kr
raj

Error after restoring source system in SAP BI side

Dear all,
i am getting issue while restoring sap source system through sap bI
"Connection LA is used in the 'LD1CLNT010'
source system as a connection 'LB1CLNT400' to BW."
Do you want to delete this connection in the source system?
Connection Is Restored After It Has Been Deleted Successfully
it asked me delete or do not delete
what to do next

hi,
you need to ensure that source system to BW is restored properly .
check in TABLE RSBASIDOC in BW through transaction se11/se16.every source system entry must be here with repect to BW.
If source system entry is missing then there are issues.Normally BASIS Team makes entry.restores system
you cn also check in RSA1-->SOURCE SYSTEM.Here u must find your R3 system name.
hope it helps
thanks,
nilesh

Upload data from legacy system to SAP through ALE IDOC

Hello All,
I have a requirement where i need to upload the data from legacy system to SAP. So i am using ALE IDOC.
In my requirement i need to extend the Standard IDOC. I have extended the IDOC and even found the exit for the updation of the extended fields to SAP. My data would be be placed in the application server.
Can anybody tell me how to retrieve the data and update in the tables for the extended fields.
Could you please provide a sample program for retrieving data for IDOC.
Thanks

Hi,
You can find the sample code in the following link.
Re: calling idoc_input_creditor
Regards
Sajid

How to UNLOCK queues when data is migrated from legacy system to SAP syste

Hi All,
I need some help regarding queues (SMQ2). XI is been used to migrate data from legacy system to SAP system. Sometimes the queue is getting locked. Once the queue is unlocked then the message is processed correctly. So, the incoming queues must be "unlocked" routinely so that they can process through the system. There is a standard report RSQIWKEX available that can be scheduled in SAP system to automatically unlock the queues. Before using the standard report RSDIWKEX, we made sure that we have added parameter MONITOR QRFC_RESTART_ALLOWED set to "1" in Integration Engine specific configuration (TCODE SXMB_ADM).We are unable to analyze the reason for locking of queues and how to avoid it. If the locking of the queues can not be avoided, is there any way to unlock the queues? We tried executing this report but were not successful in unlocking the queues. Please guide us in solving this issue. It would be really helpful if you can give us a direction in solving this problem.
Thanks in Advance,
Shwetha.

Hi,
Just check if the Queues are registered in Transaction SMQR.
If its not, then register the Queue by pressing 'Register' Button
Sharif.

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

Uploading Meter data into the system

Can some one please describe the process of uploading the meter data into CC&B.
What is the content of the flat file that i upload.can i upload a meter read XML file directly into the staging tables.....kindly explain the steps..I have not been able to upload any daat into the system using staging control and staging upload page.
Also i found out that there are batch process MUP1 and MUP2 which need be rum in order to upload the meter data into the system from the meter read staging table.Is this correct.
With regards to the meter upload staging table, i referred to the MR staging table : CI_MR_STAGE_UP
there is some data available with the installation as demo data.
For column MR_UP_STATUS_FLAG, there are values such as E, P, C...I unsersatnd there meaning.
1) For Pending P status, i submitted the batch processes MUP1 and then MUP2, expecting that teh status might change to Complete, c.......at the same time i ran MRUP-PRG ........well i was going to write nothing happened , but i saw that after some time all teh rows with ataus P and C are not present any more..........
2)How do i rectify the data with E status.........
Please helpp me uploading more data to the CI_MR_STAGE_UP Meter read staging table.

Hi,
thanks for the reply..
can u please tell me what is the content of the flat file that i upload.can i upload a meter read XML file directly into the staging tables.....kindly explain the steps..I have not been able to upload any daat into the system using staging control and staging upload page.
if u can give a flat file sample content for the meter read.
Also is it advisable to insert data into upload staging table through SQL drectly.
And can u pls tell me the difference between XAI upload staging table and other upload staging table such as for MR, FA etc.

Pricing conditions for the articles are getting triggered one day before the actual activation date to 3rd party systems through job WPMU.

Hi SAP Guru´s,
Currently we are sending the pricing, promotions & article master data delta load to 3rd party system from SAP ECC via SAP XI through IDOCS using daily scheduled batch jobs WPMU. IDOC segment - WP_PLU.
Here the issue is the promotion & pricing data are sent to 3rd party system one day before the actual start date.
Eg: Promotion 123456 which has start date as 15/05/2014 & ending on 30/05/2014 & was created & activated on 13/05/2014.
This promotion 123456 is getting triggered from SAP ECC through batch job on 14/05/2014 morning & 3rd party system receives the data on 14/05/2014 & the promotion are getting activated at 3rd party system end on 14/05/2014 itself which actually gets active from 15/05/2014.
Same in the case for Standard Pricing data which needs to be active from 31/05/2014 once the promotion 123456 ends on 30/05/2014.
The standard pricing data gets triggered from SAP ECC on 30/05/2014 through batch job & reaching 3rd party system on 30/05/2014 & getting activate on 30/05/2014 itself.
This creates more issues at the store end as well as affecting business.
We checked at 3rd party system end & they replied that their system considers the updated time stamp & date to activate the prices & it does not considers the actual active from & active to date. They need the data to be sent from SAP ECC on the effective date of the pricing & promotions.
Can any one help me how to change the pricing conditions beign triggered through batch job in SAP ECC based on the actual promotion & pricing conditons start date or is there any other process to trigger the data through the batch job on the actual promotion & pricing data activation date.
Thanks in Advance.
Thanks & Regards,
P.P.Shankar

Hello Shankar,
Change the lead time in the POS Outbound Profile. You can't put less than 2 days there so data for today and tomorrow will be transferred which also means you need to adjust your batch timing accordingly.
Sales and Distribution -> POS Interface -> Outbound -> Maintain Profile for POS Outbound.
See if it helps. The best option would still be that the 3rd part system considers the activtion date.
Kind Regards
Kaizad

Meter data aquisition system through SAP

Similar Messages

Maybe you are looking for