abap

[Former Member]

1. When we append a record to a sorted internal table how it is appended?

2. What is the standard script for picking list?

3. What is the structure of itab of screen?

4. What is the purpose of RDBMOIND RPOGRAM?

5. What is the difference between EDI AND ALE?

6. What is process code?

7. How can we enable hyperlink in screen painter?

8How can we create editor box in alv grid? Give coding?

9. Can we insert two records in internal table? if yes give code?.

10. Smart form: how to print a smart form with portrait style and landscape style at the same time?

11. How to debug an Idoc at runtime?

12. Out bound process code for quotation? Which transaction is used to make dictionary adjustments when upgrading versions of SAP?

13. What is the use of CTU_PARAMS hewn we r working with BDC?

14. What is meant stacked list?

15. What are the characteristics of a bapi?

[peter_ruiz2]

hi gopi,

3. SCREEN-NAME 30 C Field name

SCREEN-GROUP1 3 C Analysis of Modif group 1

SCREEN-GROUP2 3 C Analysis of Modif group 2

SCREEN-GROUP3 3 C Analysis of Modif group 3

SCREEN-GROUP4 3 C Analysis of Modif group 4

SCREEN-REQUIRED 1 C Required field

SCREEN-INPUT 1 C Field ready for input

SCREEN-OUTPUT 1 C Displayed field

SCREEN-INTENSIFIED 1 C Field intensified

SCREEN-INVISIBLE 1 C Field invisible

SCREEN-LENGTH 1 X Field length

SCREEN-ACTIVE 1 C Field active

[Former Member]

Hi!

1) The rows are appended at end of table.

😎 We have define a field as checkbox and editable:

DATA: gt_fieldcat TYPE lvc_t_fcat WITH HEADER LINE.

....

CLEAR gt_fieldcat.

gt_fieldcat-fieldname = 'MARCA'.

gt_fieldcat-scrtext_l = 'Marca'.

gt_fieldcat-scrtext_m = 'Marca'.

gt_fieldcat-scrtext_s = 'Marca'.

gt_fieldcat-outputlen = 10.

gt_fieldcat-tabname = 'I_DADES'.

gt_fieldcat-checkbox = 'X'.

gt_fieldcat-edit = 'X'.

APPEND gt_fieldcat.

Bye!

[Former Member]

1. -

---

Entries are inserted according to the sort sequence defined through the table key

2.----

---

rvpicksin

3..----

---

name,group1,group2,group3,group4,required,input,output,intensified,invisible,length,active,displa_3d,value_help,request

4.

The program RBDMOIND checks that the IDocs passed to the transactional RFC have already been sent to the receiving R/3 System. If they have been sent, the IDoc status is changed to "12" - Dispatch OK.

To set the IDoc dispatch status, run the program RBDOIND after the IDocs have been passed to the communication layer.

5..----

---

The philosophical difference between EDI and ALE can be

pinned as follows: If we send data to an external partner,

we generally speak of EDI, while ALE is a mechanism to

reliable replicate data between trusting systems to store a

redundant copy of the IDoc data. The difference is made

clear, when we think of a purchase order that is sent as an

IDoc. If we send the purchase order to a supplier then the

supplier will store the purchase order as a sales order.

However, if we send the purchase order via ALE to another

R/3 system, then the receiving system will store the

purchase order also as a purchase order.

6..----

---

Process of filling the IDOC with application data is done by Function Module. But, function module is not assigned to a Partner. It is encapsulated by a Process Code and this Process Code is assigned to a Partner in Partner Profile.

• Assigning Function Module to Process Code

- Go to Transaction WE41.

- Switch to “Change” Mode and click “New Entries”.

- Enter Process Code Name and assign the Function Module created.

In the partner profiles, the processing is never addressed directly but rather always using a process code. You can therefore replace an old process with a new one for any number of partners by assigning the existing process code to the new process.

there two types of processcodes

inbound

outbound

7..----

---

9.----

---

INSERT LINES OF <itab1> [FROM <n1>] [TO <n 2>] INTO <itab2>

[INDEX <idx>].

INSERT LINES OF <itab1> INTO <itab2> [INDEX <idx>].

10----

---

11----

---

IDocs are processed by a function module, which are mapped

against in table EDIFCT. When you process an IDoc with BD87

you can have a breakpoint in the function and it will stop.

For outbound processing it depends on which program is

sending the IDoc. For transactional data like purchase

orders, the IDoc is created via RSNAST00 which in turn calls

a function module assigned to the processing code (BD41).

12----

---

a)

b)the transaction is SPDD.

13. -

---

it fix the screen size

14.----

---

A stacked list is nothing but secondary list and is

displayed on a full-size screen unless you have specified

its coordinates using the window command.

15----

---

Naming Conventions

BAPIs are identified by the name of the business object type followed by the name of the BAPI. (BAPI names are in English and describe what the BAPI does to the business object). A period separates the two parts of the name.

Example

For example, the full name of the BAPI CheckAvailability() of the business object Material is Material.CheckAvailability().

Standardized BAPIs and Parameters

There are some standardized BAPIs that can be implemented for most business object types. These BAPIs have specific functions, for example, the BAPI GetList(), retrieves a list of the instances of a business object type.

These BAPIs are implemented according to specified rules and have the same name for all business objects. The BAPI GetList() can be used for many business objects, for example, CompanyCode.GetList() and Material.GetList(). For information about these BAPIs see Standardized BAPIs.

As far as possible, the parameters of BAPIs are also standardized. Standardized Parameters that can be implemented and defined for BAPIs are used in the BAPI interface.

Database Consistency

Each BAPI that creates an instance of an object or updates the data of an object is responsible for database consistency. All database changes are carried out completely or not at all.

However, the COMMIT WORK command must not be executed by the BAPI itself; it must be executed by the calling program. For further information see the Transaction Model for Developing BAPIs.

No Dialog Orientation

BAPIs do not return any screen dialogs from the SAP server system to the calling application.

Authorization

To interact with an SAP System, users must have a certain set of authorizations. To execute a BAPI as part of your application program, the users of your application must have the appropriate authorizations set up in their SAP master records. The documentation provided with the BAPI contains information about the required authorizations.

Any attempts to execute a BAPI that fail as a result of insufficient authorization are reported back to the calling application.

Data Types and Data Display

BAPIs are programming interfaces for business applications. Neutral (internal) data types and data formats are therefore used almost exclusively in BAPI interfaces. There are some exceptions, for example:

• Currency codes

• Internal keys

• Quantities

• Specific fields in address structures

For information about these exceptions see Structure link Internal and External Data Formats in the BAPI Programming Guide.

Conversion BAPIs are provided for the appropriate conversions between internal and external formats. For information see Service BAPIs for Help Functions.

BAPI parameters can use most of the data types supported by SAP. The data types are documented in the structure entries of each parameter in the ABAP Dictionary.

Processing Modes

When BAPIs are called directly, for example with the BAPI ActiveX Control, the SAP DCOM Component Connector, or by directly calling the underlying function module, they are processed in synchronous mode.

For information about calling BAPIs in a distributed environment (ALE) see Programming Distributed Applications.

Business Object Attributes

The attributes of business objects are accessed through the BAPI interface itself. An example of a BAPI that retrieves such attributes is GetDetail() of the business object CompanyCode.