Please Provide a Key for SAP Predictive Analysis 1.15 32-bit

please provide a needed a key for SAP Predictive Analysis 1.15 32-bit to be used in University Lab computers.

Hi Ye,
I am afraid but the only way today is to delete your document without PA / Lumira.
By default, local files are stored at :
User/Documents/SAP Lumira Documents
In this folder you'll see the list of all the documents you have created with SAP Lumira or SAP PA.
Delete the document that you don't want anymore and (re)start SAP PA.
The delete functionnality from the desktop tool is an idea accepted by the Labs (Delete Files in Lumira Desktop : View Idea), but not implemented yet.
Hope it helps,
Edouard

Similar Messages

Can i use SAP Predictive Analysis for this scenario?

Hi guys. I'm new in this subject so I'm a little bit confused about in which cases SAP Predictive Analysis is helpful?
Could it be helpful for this case? I have prices of rice for differente years, from 2007 to 2013. Can SAP Predictive Analysis help me forecast what will be the price of rice for 2014, 2015 and so on?
Which algorithm should I use? Does it come integrated in the tool or is it an add-on?
I´ll appreciate it very much if you could send me the right steps to achieve this.

Hi Erika,
SAP PA has only Triple exponential smoothing algorithm; In most cases, single exponential smoothing would not make any sense [this is available through HANA PAL or R integration with SAP PA];
If you have R integration you should see something like this
In Single exp smoothing only alpha is used;
in double exp smoothing alpha and gamma is used; and all three in gamma.
Why these alpha, beta and gamma... has a big derivation to understand; [let me know if you need any document, I have compiled as on some reference]
What values alpha, beta and Gama should hold in Triple ... or what is the right value, .... actually there are no right value and wrong value for them.
... as for the steps to go in SAP PA, refer below:
Please let me know if you need any assistance ...
Regards,
Arvind E

Nothing displays on Predictive part in SAP Predictive Analysis

Hi,
Earlier, I created a predictive analysis using R-K Means algorithm, and the result was displayed a week ago and saved it. I opened it several times, trying to beautify the same. But today when I opened it, nothing is seen and also I am unable to add analysis as well. I am using SAP Predictive Analysis version 1.16.0.
Please help me how to resolve the issue.

Hi Anita, in case this has not be resolved, i just had this issue this morning.
I was unable to add or see any Analysis in Predict Tab.
It seems that if you supress your preference settings
(in C:\Users\yourName\.sapvi\predictive_preferences)
including links to all of your documents, and "repairing" Predictive Analysis by Re-installing it, it works again .
It also seem, after reimporting the original issue document, it is blasted, so you'll have to redo it from scratch.
Hope it will work for you, notice me if it does !
Guillaume BUNEL

SAP Predictive Analysis 1.20 download

Hi SCN,
Has anyone tried SAP Predictive Analysis 1.20 ??
Please share me the link to download the 1.20 Version .
Regards
Sateesh

Hi Sateesh,
Are you looking for a trial version?
I am not aware of direct evaluation download of 1.20. But you should be able to upgrade an earlier version simply though the menu
Help -> Check for updates
Greetings
Andreas

SAP Predictive Analysis error while executing KNN algorithm

Hi ,
I am getting 'duplicate column name' error, while implementing knn algorithm in SAP Predictive Analysis. Please help me
Please look into my screenshots for configurations.
I am taking the data from database.
Thanks
Niyati
Message was edited by: Niyati Priyadarshinee

Hi Niyati,
SYSTEM user has not given you rights to create repository so you are facing this issue, Ask appropriate rights from your SYSTEM user.
He can either execute below statement
GRANT REPO.EDIT_IMPORTED_OBJECTS ON "'afl.falcon'" TO lui;
or
he can go to Security-> Users under Package Privilege add Root package then on right side he can assign the roles.
**** Also Add Repository_Rest procedure under Object Privilege tab
Regi id by default included in latest versions of HANA Studio. No need to map it manually
Thanks
Bhupender

Access key for SAP 4.6C IDES

Hi,
Can any body send me the access key for SAP 4.6C IDES?
I am unable to proceed further because of it.
Please mail me that if you have to:
[email protected]
Regards,
lokesh

Hi
You have to ask the person from whom you got this software of SAP IDES
He will provide the Access key.
Reward points for useful Answers
Regards
Anji

Using Multiple Linear Regression from SAP Predictive Analysis within S&OP

How could I go about using a model exported from SAP Predictive Analysis, say a multiple linear regression model, as a stored procedure in HANA from within S&OP?

Hi Kevin,
You cannot use a model exported from SAP Predictive Analysis in S&OP. S&OP uses the same PAL libraries from HANA for Statistical Forecasting. We enable a few statistical forecasting methods from PAL like exponential smoothing from S&OP.
Thanks,
Raghav

Using Solution Manager 7.0 to Generate Solution Key for SAP Netweaver 7.3 ?

Hi, SDN Gurus.
We are running Solution Manager 7.0.
I am trying to generate solution key for SAP Netweaver 7.3 system. When I was creating a new system (in TCode SMSY); I only see Newtweaver 7.1 is the latest version available in the SAP Netweaver product version drop down list.
Is that true that I always need to upgrade the latest/compatible version (SP & patches) of SAP Solution Manager to generate solution key for the latest released of SAP products?
If this is the case, what version of SAP Solution Manager I need to create new system and generate solution key for SAP Netweaver 7.3?
Thanks for advices,
KC

Hi,
Please follow the note [Note 1274430 - Installation of Solution Manager 7.0 Stack 18 and higher|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1274430]
and the discussions here [Direct Upgrade from Solution Manager SP16 to SP26|Direct Upgrade from Solution Manager SP16 to SP26]
Thanks,
Jansi

SAP Predictive Analysis and SAP Infinite Insight Product Road Map

Hi everyone,
where can I find the current SAP Predictive Analysis and SAP Infinite Insight Product Road Map?
The latest version I found on SCN is from Dec. 2013.
Best Regards,
BJE

Hi,
The Predictive Analysis and InfiniteInsight road map was updated on SMP Sep 29:
https://websmp209.sap-ag.de/~sapidb/011000358700001160102012E.pdf

Can you please provide the information for writing ocp

Hi,
Iam planning to write OCP exam, can you please provide the information for it.
what are the courses i need to take.where can i get the study material for it.
Looking forward for your reply

The 9i OCP track is 2 plus 2 exams plus a hands-on course. Follow the links you got above.
The best study material, if you really want to study and get to know the stuff, is available here on OTN. Download and practice the Database together with reading the Concepts, SQL Reference, Admin and Performance tuning guides from 10g or 9i libraries.
Use the Search to lookup concepts, syntax etc.

Do we need License Key for SAP IK

HI,
Do we need to request for License Key of SAP Integration Kit and add in License Keys in CMC of BO EDGE 3.1.
Early response is appreciated.
Thanks,
Bharath

Hi Ingo,
Thanks foy your reply.
IS The License Key which we downloaded from Market Place is enough for SAP IK or do we need to Raise a request for New License Key For SAP IK
Thanks,
Bharath

May you please provide some information for Cisco 1600 AP is better than Juniper AP ?

Hello all,
May you please provide some information for Cisco 1600 AP is better than Juniper AP ?
I would like to know some comparison test between Cisco 1600 AP with Juniper AP.
Thanks very much !
Crows

you cannot compare like this you need to compare it with model by model just compare the data sheet of both .But remeber cisco has larger portfolio and is ranked better then juniper in Gartner report 2013 you can you that in reference.
********Do rate helpful posts*************

Does SSO2 provide SSO Support for SAP BOBI 4.x Applications?

I could not find any referrence in SAP BI BI 4.x documentation for SSO where this SSO2 would be mentioned!
- Wobi

Hi,
Does SSO2 provide SSO Support for SAP BOBI 4.x Applications?
BOBJ == SAP BusinessObjects Business Intelligence platform?
SSO2 == SAP Single Sign-On?
If yes, BusinessObjects Business Intelligence platform delivers historically its own basis SSO based on Kerberos (but only for applications running on BOBJ platform). I recommend to use it if it fits to your requirements. If not, you can configure "Trusted Authentication". In this case BOBJ trusts the authentication of the web applications server. Here you can use SAP Single Sign-On with SAML or certificates.
Regards
Matthias

Please provide me material for bdc

Hi everyone,
can you please provide me some stuff for bdc, actually i am working on bdc for mm01 , so plz send me study materials and if you have any scenario then please forward me.
Thanks & Regards,
Vimarsh B.

Hi
Hope it will help you.
Reward if help.
BATCH DATA COMMUNICATION
About Data Transfer In R/3 System
When a company decides to implement the SAP R/3 to manage business-critical data, it usually does not start from a no-data situation. Normally, a SAP R/3 project comes into replace or complement existing application.
In the process of replacing current applications and transferring application data, two situations might occur:
u2022 The first is when application data to be replaced is transferred at once, and only once.
u2022 The second situation is to transfer data periodically from external systems to SAP and vice versa.
u2022 There is a period of time when information has to be transferred from existing application, to SAP R/3, and often this process will be repetitive.
The SAP system offers two primary methods for transferring data into SAP systems. From non-SAP systems or legacy system. These two methods are collectively called u201Cbatch inputu201D or u201Cbatch data communicationu201D.
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 u201Cdata transferu201D 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:
u2022 To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
u2022 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:
u2022 The transaction code, if you do not already know it.
u2022 Which fields require input i.e., mandatory.
u2022 Which fields can you allow to default to standard values.
u2022 The names, types, and lengths of the fields that are used by a transaction.
u2022 Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
u2022 Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System u2013 Status.)
u2022 Step through the transaction, entering the data will be required for processing your batch input data.
u2022 On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
u2022 Display these by choosing System u2013 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.
u2022 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 youu2019ll 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.
u2022 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:
u2022 Create a BDCDATA structure
u2022 Write the structure out to a session or process it with CALL TRANSACTION USING; and then
u2022 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:
u2022 Data that is entered into screen fields.
u2022 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:
u2022 PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
u2022 DYNPRO: Screen Number. Set this field only in the first record for the screen.
u2022 DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to u2018 u2018 (blank) for all other records.)
u2022 FNAM: Field Name. The FNAM field is not case-sensitive.
u2022 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:
u2022 User Name: User name
u2022 Group: Name of the session
u2022 Lock Date: The date on which you want to process the session.
u2022 Keep: This parameter is passed as u2018Xu2019 when you want to retain session after
processing it or u2018 u2018 to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
u2022 Tcode: Transaction Name
u2022 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 u2013 1 is transaction code.
Parameter u2013 2 is name of BDCTAB table.
Parameter u2013 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 u2013 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 u2013 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.
u2022 Click Get Transaction.
u2022 Return to BI.
u2022 Click overview.
u2022 Position the cursor on the just recorded entry and click generate program.
u2022 Enter program name.
u2022 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.
u2022 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.
u2022 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.
u2022 Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
u2022 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.
u2022 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 donu2019t 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.
AN EXAMPLE WITH SESSION METHOD
Following program demonstrates how data is passed from flat file to SAP transaction and further to database table by using SESSION method.
The transaction is TFBA (to change customer).
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.
Flat file can be created in your hard disk as follows:
1 Vinod Hyderabad
2 Kavitha Secunderabad
3 Kishore Hyderabad
(Where 1st character field is Customer number, 2nd field is Customer name and 3rd field is City.)
To transfer this data to database table SCUSTOM following interface can be used.
REPORT DEMO1.
Following internal table is to upload flat file.
DATA: BEGIN OF ITAB OCCURS 0,
ID(10),
NAME(25),
CITY(25),
END OF ITAB.
*Following internal table BDCDATA is to pass date from internal table to session.
DATA: BDCTAB LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
Variables
DATA: DATE1 LIKE SY-DATUM. DATE1 = SY-DATUM - 1. u201C This is for Hold Date
To upload flat file to internal table.
CALL FUNCTION UPLOAD
EXPORTING
FILE NAME = u2018C:\FF.TXTu2019
FILE TYPE = u2018ASCu201D
TABLES
DATA_TAB = ITAB
EXCEPTIONS
CONVERSION_ERROR = 1
INVALID_TABLE_WIDTH = 2
INVALID_TYPE = 3
NO_BATCH = 4
UNKNOWN_ERROR = 5
OTHERS = 6.
If sy-subrc = 0.
Calling Function to Create a Session
CALL FUNCTION u2018BDC_OPEN_GROUPu2019
EXPORTING
CLIENT = SY-MANDT
GROUP = u2018POTHURIu2019
HOLDDATE = DATE1
KEEP = u2018Xu2019
USER = SY-UNAME
EXCEPTIONS
CLIENT_INVALID = 1
DESTINATION_INVALID = 2
GROUP_INVALID = 3
GROUP_IS_LOCKED = 4
HOLDDATE_INVALID = 5
INTERNAL_ERROR = 6
QUEUE_ERROR = 7
RUNNING = 8
SYSTEM_LOCK_ERROR = 9
USER_INVALID = 10
OTHERS = 11.
If sy-subrc = 0.
*-- MAIN Logic--
LOOP AT ITAB
PERFORM GENERATE_DATA. u201C Populating BDCDATA Table
CALL FUNCTION u2018BDC_INSERTu2019
EXPORTING
TCODE = u2018TFBAu2019
TABLES
DYNPROTAB = BDCTAB
EXCEPTIONS
INTERNAL_ERROR = 1
NOT_OPEN = 2
QUEUE_ERROR = 3
TCODE_INVALID = 4
PRINTING_INVALID = 5
POSTING_INVALID = 6
OTHERS = 7.
REFRESH BDCTAB
ENDLOOP.
Calling function to close the session
CALL FUNCTION u2018BDC_CLOSE_GROUPu2019
EXCEPTIONS
NOT_OPEN = 1
QUEUE_ERROR = 2
OTHERS = 3.
Endif.
Endif.
*& Form GENERATE_DATA
Create BDC Data
FORM GENERATE_DATA
Passing information for 1st screen on BDCDATA
BDCTAB-PROGRAM = u2018SAPMTFBAu2019.
BDCTAX-DYNPRO = 100.
BDCTAP-DYNBEGIN = u2018Xu2019.
APPEND BCDTAB.CLEAR BDCTAB.
Passing field information to BDCDATA
BDCTAB-FNAM = u2018SCUSTOM-IDu2019
BDCTAB-FVAL = ITAB-ID.
APPEND BDCTAB.CLEAR BDCTAB.
Passing BDC_OKCODE to BDCDATA
BDCTAB-FNAM = u2018BDC_OKCODEu2019.
BDCTAB-FVAL = u2018/5u2019.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information for next screen to BDCDATA
BDCTAB-PROGRAM = u2018SAPMTFBAu2019.
BDCTAB-DYNPRO = 200.
BDCTAB-DYNBEGIN = u2018Xu2019.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information to BDCDATA
BDCTAB-FNAM = u2018SCUSTOM-NAMEu2019.
BDCTAB-FVAL = ITAB-NAME.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information to BDCDATA
BDCTAB-FNAM = u2018SCUSTOM-CITYu2019.
BDCTAB-FVAL = ITAB-CITY.
APPEND BDCTAB.CLEAR BDCTAB.
Passing BDC_OKCODE to BDCDATA
BDCTAB-FNAM = u2018BDC_OKCODEu2019.
BDCTAB-FVAL = u2018SAVEu2019.
APPEND BDCTAB.CLEAR BDCTAB.
ENDFORM. u201CGENERATE_DATA
AN EXAMPLE WITH CALL TRANSACTION
Same steps to be repeated for CALL TRANSACTION
The only difference between the two types of interface is in Session method, you create session and store information about screen and data into session. When session is processed the data is transferred to database. While in CALL TRANSACTION, data is transferred directly to database table.
REPORT DEMO1.
Follow above Code till MAIN Logic. Even the Subroutine should be copied
LOOP AT ITAB
PERFORM GENERATE_DATA, u201CPopulating BDCDATA Table
Call transaction u2018TFBAu2019 using BCDDATA Mode u2018Au2019 Update u2018Su2019.
REFRESH BDCTAB
ENDLOOP.

Can someone please provide *complete* instructions for taking fullpage screenshots using Developer Toolbar?

Two additional notes:
1. I've found and typed in numerous other examples and absolutely NOTHING has worked. I keep getting "too many arguments" and am thisclose to lighting a torch to Firefox (and also for not providing this information - easily findable - by themselves!). :(
2. Therefore, please make whatever you provide:
a. valid for Firefox 28.0 and (few) previous version(s), and
b. literally broken down into single steps (consisting of ONE action each) so that literally ANYone can follow and EXACTLY duplicate what you are doing. If Grandma can't follow your directions to a perfect result, you're not done! ;)
Many thanks from myself and other frustrated users! :D

UNFORTUNATELY, WHAT YOU'VE SUPPLIED IS MORE OF THE EXACT SAME THING THAT I'VE BEEN SEEING ALL AFTERNOON AND EXACTLY NOTHING LIKE I ASKED FOR, WHICH WAS:
1. TYPE IN FIRST ITEM OF TOTAL COMMAND; YOU WILL THEN SEE X
2. TYPE IN SECOND ITEM OF TOTAL COMMAND; YOU WILL THEN SEE X, ETC.
WHY THIS IS IMPORTANT WILL BECOME SELF-EVIDENT IN FURTHER COMMENTS BELOW....
You can invoke the screenshot command by typing the first letters of the command and press the Tab key to accept the proposed suggestion.
THAT RARELY IF EVER WORKS; I MUST TYPE OUT THE ENTIRE WORD.
https://developer.mozilla.org/Tools
https://developer.mozilla.org/Tools/GCLI
I HAVEN'T YET EXAMINED THESE, BUT MY FEELING IS THAT IT WILL BE MORE OF THE SAME.
Type a space and two hyphens (--) to see the options list and use the Tab key to copy the highlighted entry (fullpage) to the command line.
TAB REALLY DOES ABSOLUTELY NOTHING FOR ME IN THIS CONTEXT.
Note that the fullpage command also has its own options, so you can type the two hyphens another time to see those options.
The default file name is "Screen Shot yyyy-mm-dd at HH.MM.SS.png" in the default Download directory.
See also help screenshot
screenshot --fullpage fullpage_screenshot.png
THE LINE ABOVE IS EXACTLY WHAT DOES NOT WORK.
IF I COPY-PASTE IT IN, A SPACE GETS ADDED. HITTING ENTER RESULTS IN IMAGE 1 (ATTACHED), FOLLOWED BY IMAGE 2 (ATTACHED) WITH ENTER AFTER BACKSPACE TO GET RID OF THE SPACE.
IF I ACTUALLY TYPE IT IN, HITTING ENTER RESULTS IN IMAGE 2.
THE "TRUE" OPTION ALWAYS COMES UP WITH ME UNABLE TO SELECT IT AS SHOWN IN IMAGE 3, LEADING AGAIN TO THE OBSERVED FAILURE MESSAGE IN IMAGE 2.
NOW YOU UNDERSTAND WHY I'M FURIOUS BY NOW! :(
screenshot --fullpage --clipboard true
screenshot --clipboard true --delay 5

Please Provide a Key for SAP Predictive Analysis 1.15 32-bit

Similar Messages

Maybe you are looking for