How to Define Access Sequence & Condition Table in SAP V/05, M/03

Define Access Sequence

To define and maintain access sequences, you need to follow a few simple steps.
Step 1) Go to SPRO > Materials management > Purchasing> Conditions> Define price determination process> Define access sequences.
As shown below , you will find a dialog structure of Access sequences, Accesses and Fields.

1. Choose the Access sequence you want to maintain (PB01 gross price).
2. Double click the Accesses folder in the dialog structure.

Step 2) In the next step you define access methods for the access sequence. You can see that several access methods are present for one sequence.
Every one of them is exclusive. It means that if a record is found in first access (Contract item), meaning that if the system finds a condition available from the Contract item, it will not search further, and that value will be used. If not, system will follow the other accesses in order to find appropriate entry.
You can also set a requirement for an access method to be used. For example, there is a requirement 35 assigned to access 10, which uses condition table 17 - Material Info Record (Plant-Specific).

A requirement for access number 10 is 35 - Plant info record. If there is no plant info record for the combination of the values in table 17, access 10 will not be used at all.

Step 3)

1. Select the access you want to modify.
2. Choose the lowest level folder in dialog structure - Fields.

Step 4)

1. You can see we are located on the details screen for access sequence PB01, access 20 and table 18.
2. The key fields of a condition table used in the condition access are showed here.

Condition table consists of condition fields which have certain attributes assigned to them. When the system tries to access a condition record it uses these attributes.

• Special value source – this field contains a value to be used as default while accessing (e.g. using a fixed info record category for the access sequence)
• Init – if this box is checked system will allow initial value for this field while accessing the condition table. If not system will not process the condition table lookup.
• Atyp – processing type in access. You can specify if the field is relevant for condition access if it is part of a free or fixed key type. Default is left blank (fixed key type).
• Priority – priority of a field (characteristic), it can be set from 01 to 99. Most of the time this field is left blank.

Define condition tables

Now, when we know what is a condition table, what it is used for, we can see where a condition table can be defined, and what option we have while creating it.
As you have seen in the previous topic, we have used table 18 – Material Info Record in our example.

Let's see where and how it is defined.
Step 1)

1. Execute the transaction code V/05 and on the initial screen enter our table number - 18.
2. In the section 2, you can see our table definition, table number, description, and two options that can be selected. First means use of the validity period (always recommended) and the other is a check for release status of the record. If checked, only released info records will be taken into account while searching for the condition.
3. Here is the list of fields you have already seen in the Define access sequence topic.

You can see how is the table defined for later use in customizing the access sequence.

V/05 transaction is used for displaying a condition table.
V/04 transaction is used for changing a condition table.
V/03 transaction is used for creating a condition table.
Now you can define a new condition table if it is required, in order to use it in the access sequence definition. Most of the times new access tables aren't required since a vast number of predefined tables.
Step 1)

1. Enter t-code M/03 and execute it.
2. Choose your new table number (must be unused, e.g. 818).
3. If you want to copy an existing table into your new table, you can select the source table here. This is useful if your table is similar to another existing table, and needs only a simple change to fulfill the requirements.

Step 2) On the next screen, you can do all of the settings for a condition table, and generate it.

1. Click this button if you want to edit the description.
2. Choose if your table should check validity periods and release statuses.
3. List of current fields. You can select any field you want to remove (by single clicking it) and choose the remove icon (List icon with a red minus sign).
4. You can add fields from field catalog by double clicking them.
5. You need to generate the table in order for it to be used by pricing functions.

You can also use right click to delete or add a field to your table, as well as to navigate the Field catalog on the right side of the screen. Not all of the fields can be shown in a single page of field catalog.

After successful creation, you will be prompted to create a change request and afterwards, you will be presented a log screen like you can see on the following screen.

You have successfully generated a condition table let's see if we can see it in the access sequence maintenance screens.

It's there, so now we can create an access using this table. We will not cover this in detail as it is extremely straight forward process.

On the accesses node of our access sequence, choose New entries button. You can create access like in the below screen for Testing purposes.

Fields should also be assigned to our access PB01 – 96 in order for it to work properly
Defining of condition types can be done in few simple steps.
Step 1)
In the IMG, click on the define condition types option.

Step 2)
Choose Define Condition Type option.

Step 3)
You can find all of the existing entries for condition types.

1. Click on the desired condition you would like to change.
2. Click this icon to choose the selected condition and enter the change mode.
3. If you want to create a new entry click on New entries. In this case, you don't have to select any existing entries.
4. If you want to create a new condition type by copying an existing condition type (it will inherit it's setting which you can change – just like copying a condition table in the previous topic), you can choose this icon – copy condition type.

You have several more actions at your disposal: deletion, selecting all condition types, deselecting all condition types.

If you select multiple condition types, you can edit them all by navigating through them in the following screen (arrow left and right or F7 and F8).
This screen has a lot of settings for a condition type, let's review the most important.
Step 4)
First section of the screen contains condition type PB00, description, and access sequence used for condition determination.
A) Control data 1 section contains the following:

1. Condition class (e.g. prices, discounts, taxes)
2. Calculation type (e.g. quantity, percentage, fixed amount, formula)
3. Condition category (e.g. basic price, input tax)
4. Rounding rule (e.g. commercial, round up, round down)
5. Plus/minus (indicates if a condition can be positive, negative or both)

B) Group condition section:

1. Group condition (indicates if a condition calculates its value by more than one item in the document)
2. RoundDiffComp (rounding difference comparison)
3. Group condition routine (routine that calculates the value)

C) Changes which can be made section:

1. Manual entries (e.g. no limitations, not possible, manual entry has priority)
2. Header condition (indicates if a condition can be used at header level)
3. Item condition (indicates if a condition can be used at item level)
4. Delete (indicates if a condition can be deleted)
5. Amount/percent (can amount/percentage be changed)
6. Value (can value be changed)
7. Qty. relation (can conversion factor between UoMs be changed during processing)
8. Calculat. Type (can calculation type be changed during processing)

 

Step 5)

The other section on the lower end of the same screen are:
D) Master data section:

1. Valid to (default date to use)
2. Pricing Proc. (pricing procedure to be used for this condition type)
3. Pricing Proc. (pricing procedure to be used for this condition type)
4. Delete fr. DB (deletion procedure for this condition type)

E) Scales section:

1. Scale basis (e.g. quantity scale, value scale)
2. Check value (default blank)
3. Scale type (controls the validity of the value/quantity)

F) Control data 2 section:

1. Currency Conv. (indicates if currency conversion is allowed)
2. Accruals (if you check this box you indicate that it is a statistical condition)
3. Promotion condition (is this condition relevant only for promotions)
4. Quantity conversion (controls how quantity conversion will be processed)
5. Exclusion (condition exclusion indicator – e.g. gross price, tax code, delivery cost)
6. Rel.Acc.Assig (determines if the condition type is relevant for account assignment)

When you are done with creating, changing or copying of the condition type, you can save your changes.

SAP Output Processing – SAP Output Message with SAP NACE

Sap Output Message: (SAP NACE) This article will explain how to Create New Output Type for a SAP Output Message with NACE Tcode.
It is well detailed with Step by Step tutorial with all the customizing to be done. This guide will guide from 0 to full New Output Message Type working.
As extra, I joined at the end a Troubleshooting session for the most common issue when dealing with NACE Tcode and SAP Output Message.
In Order to have a relevant sample, let’s take the example of custom Message Type for SAP Sales Documents.

If you have a question or a requirement about this topic, feel free to leave a comment and I will do my best to answer.

Table of Contents

Table of Contents
• Create a New sap output message Type
  • Call NACE Tcode and Go to Output Types
    • Change display mode to edit mode then Create New entry
    • Fill ID of SAP Outout Message Type, description and access type
    • Set NACE Output Type Dispatch Time for sap output message
    • Set Message Transmission Medium
    • Specifies how the output will be produced.
    • Set Processing routines
    • Set Partner Functions Determination
    • Create Condition Records
  • Create Output Procedure
    • Assign Output Procedure to Transaction Type

Create a New sap output message Type

Call NACE Tcode and Go to Output Types

Launch the SAP Transaction Code NACE for Conditions for Output Control.
First let’s select the Output Types as following and The Application ( for Sales, Application is V1 )

Change display mode to edit mode then Create New entry

Fill ID of SAP Outout Message Type, description and access type

Set NACE Output Type Dispatch Time for sap output message

You can process a message immediately by updating the application document or you can process it at a later time. For later processing you must use the report program RSNAST00 or a corresponding application function.

1. Send with periodically scheduled job: The message is processed through report program RSNAST00. This report program can be scheduled periodically or started manually
2. Send with job, with additional time specification: As in time 1, but the message contains an earliest processing date and a requested processing time. The message is ignored by report program RSNAST00 before the requested date.
3. Send with application own transaction: The message is selected and processed by application specific programs. Processing can take place online or in the background
4. Send immediately (when saving the application): The message is processed when the application document is saved. No further processing of the message is necessary

Set Message Transmission Medium

Specifies how the output will be produced.

You can specify, for example, that the output is printed or that it is produced and sent by other means, such as fax, electronic mail, or electronic data interchange (EDI/ IDoc). 
Set Partner Function

a sample list of used function partner in Output Type.

1. SP: Sold-To Party
2. BP: Bill-to Party
3. SH: Ship-To Party
4. PY: Payer
5. LS: Logical System 
6. ..

Set Processing routines

For each Transmission Medium, a processing routines must be configured. For this sample, the Output Type triggers an IDoc with the program RSNASTED within the routine EDI_PROCESSING.

You can left all the rest of tabs blank.
When Saving, SAP will ask you for customization request. ( Good point : Nace Configuration in transportable )

Set Partner Functions Determination

Create Condition Records

Go Back to NACE transaction and select Condition Records
Remember we have configured the Access sequence defined in a previous step , create condition for output type.

Create Output Procedure

Go Back to NACE transaction and select Procedures

Assign Output Procedure to Transaction Type

Go to SPRO customizing and find where the customizing point to Maintain Output Determination
Test Output Message
Here the last step. test you output message and check if the SAP Output processing in well done.
(For Order, par example,  try to modify an SAP order, then saved. Go to message > Header > and check the output processing if it is green )

Troubleshooting

If Message Output doesn’t appear in Header>Message on Transaction, verify these point:
– Is record conditions meet the creteria of the transaction ?
– Is record conditions maintained ?
If you can add manually the Output Type you have created, make sure this Output is used on Output Procedure ( NACE) active for the transaction type ( SPRO )

SAP Tables and the data dictionary

SAP tables are created, displayed and maintained via the SAP data dictionary using transactions such as SE11 and SE80 and are the building blocks of the SAP environment. It is where all the data within your SAP system is stored ready to be processed or accessed via your ABAP code. But it's not just business data like tables such as MARA and MARC that store material details or EKKO and EKPO that store purchasing details but also the core info that essentially makes up the system.

For example when you create an ABAP report/program this code is then stored within a database table. Also the metadata of tables is also stored in database tables. For example DD02L stores the global settings and attributes for each table, DD03L stores the list of fields that make up the table. The details about each of these fields are also stored in a variety of tables depending how the field is made up.

Give it a try, via transaction SE11 (or SE80) create a new Z table and see if it appears in table DD02L and if the fields appear in DD03L.

So as you can see there is a lot of complicated interlinked information stored in hundreds of thousands of tables! But how do you know what is stored in what? Well the simple answer is experience plays a big part and is also why you get a lot of specialisation in SAP. Because along with all these tables there are many transactions that allow a user to add, maintain and process the data.

But this is also where SE80.co.uk can help, providing information of all these database tables (also includes Structures and Views). This allows you to be able to perform a simple keyword search (i.e. table name/title) and view the details of each table on one page including details such as:

• Table name
• Title
• Delivery class
• Text table if appropriate
• Field list
• Key field indicator
• Data element
• Data type
• Length
• Check table
• Field description
• Includes
• Link to full details about each field/data element/domain


Add data to SAP tables
Also on a slightly related topic there are two basic ways you can add data to a database table within your SAP system. The first method is manually via transactions such as SM30, SE16, SE80 etc. and the second method is via ABAP code inserted into a program or report.
• Add data manually via SAP tcode
• Create ABAP code to add data


SAP Tables by Module area
Purchase Order Tables
Project Systems Tables
SAP MM Tables - Material Management
SAP BC Tables - Basis Components


Popular SAP tables
A000
Condition Table for Pricing

PA0000
HR Master record tables(info types for PNP ldb)

COVP
CO Object: Line Items (See FM HRGPBS_DRILL_READ_COVP)

EKKO
SAP ALV test reports

DD02V
Data dictionary tables

TRDIR
Table of SAP programs

USR02
Logon data

internal table as an SAP search help.

F4IF_INT_TABLE_VALUE_REQUEST sap function module

The below code shows how function module F4IF_INT_TABLE_VALUE_REQUEST is used to display a basic ABAP internal table as an SAP search help. The users selection is then passed into a selection screen parameter.

*&-------------------------------------------------------------*
*& Report  ZTAB_SHELP                                          *
*&-------------------------------------------------------------*
*& Created by erpworkbench.com                                     *
*&                                                             *
*& Display itab as search help                                 *
*& ...................................                         *
*& The basic requirement for this demo is to display a number  *
*& of fields from the EKKO table as a search help using        *
*& SAP function module F4IF_INT_TABLE_VALUE_REQUEST.           *
*&-------------------------------------------------------------*

REPORT ZTAB_SHELP.

parameters: p_ebeln type ekko-ebeln.

TYPES: BEGIN OF t_ekko,
  ebeln TYPE ekpo-ebeln,
  ebelp TYPE ekpo-ebelp,
  statu TYPE ekpo-statu,
  aedat TYPE ekpo-aedat,
  matnr TYPE ekpo-matnr,
  menge TYPE ekpo-menge,
  meins TYPE ekpo-meins,
  netpr TYPE ekpo-netpr,
  peinh TYPE ekpo-peinh,
 END OF t_ekko.

DATA: it_ekko TYPE STANDARD TABLE OF t_ekko INITIAL SIZE 0,
      wa_ekko TYPE t_ekko,
      it_return type STANDARD TABLE OF DDSHRETVAL,
      wa_return like line of it_return.

**************************************************************
*at selection-screen
at selection-screen on value-request for p_ebeln.

select *
  up to 10 rows
  from ekko
  into CORRESPONDING FIELDS OF TABLE it_ekko.

CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
  EXPORTING
*   DDIC_STRUCTURE         = 'EKKO'
    RETFIELD               = 'EBELN'
*   PVALKEY                = ' '
*    DYNPPROG               = sy-repid
*    DYNPNR                 = sy-dynnr
*   DYNPROFIELD            = 'EBELN'
*   STEPL                  = 0
    WINDOW_TITLE           = 'Ekko Records'
*   VALUE                  = ' '
    VALUE_ORG              = 'S'
*    MULTIPLE_CHOICE        = 'X'  "allows you select multiple entries from the popup
*   DISPLAY                = ' '
*   CALLBACK_PROGRAM       = ' '
*   CALLBACK_FORM          = ' '
*   MARK_TAB               =
* IMPORTING
*   USER_RESET             = ld_ret
  TABLES
    VALUE_TAB              = it_ekko
*    FIELD_TAB              = lt_field
    RETURN_TAB             = it_return
*   DYNPFLD_MAPPING        =
 EXCEPTIONS
   PARAMETER_ERROR        = 1
   NO_VALUES_FOUND        = 2
   OTHERS                 = 3.

READ TABLE it_return into wa_return index 1.
p_ebeln = wa_return-fieldval.

 

How to change Transport request from Released to Modifiable

How to change Transport request from Released to Modifiable

I think I don’t have to write anything about this document title itself is sufficient to know what I am going to show you guys.

Sorry forgot to write one comment :::: Please no nonsense with this. It is the way to just rectify the mistake if u mistakenly released the Request.
Once the request is imported to any other system, do not use this. Import buffers may have problems.


Step 1: Go to SE38 – Execute Program RDDIT076.

Step 2: Give your released requests number and execute again.



Step 3: After executing, you will get the list of all tasks from the Transport request.  

Step 4: Double click on every Task and change the Status from R è D.   And save it for all the task and request.




--------------------

Hi Experts,
I will explain the procedure for changing released TR into unrelased TR. i.e; modifiable state. There is no option given explicitly for chaning the released TR into unreleased TR in STMS or SE01 Transactions. we have to follow the below steps.
1. Go to SE38
2. execute the report RDDIT076

3. now, we will get the below screen which asks for TR/Tasks . give the released TR number and execute (F8)

4. Once executed, you will get the below window,

5. first we need to change the task to unreleased. double click on the task number. now, click on the pencil button to enter edit mode.then click on input help on the filed “Status”

6. change the status from “R” to “D” and save

7. now repeat the steps 5 and 6 for Transport request. finally the status column should be in “D” as shown in below.
8. now goto SE01 or SE09, type the TR number and check. it will be in modifiable state.

Once you changed the TR into modifiable, you can change objects in the TR. you have to again release the task and TR.However, once we changed the released TR into modifiable, you can’t release the TR again and you will be getting an error “Request <Request ID> has the invalid attribute EXPTIMESTAMP”

you have to double click on the TR, navigate to the properties tab. enter into edit mode. you can see “Attribute” column in the screen.

Select the row “EXPORT_TIMESTAMP” and delete that row. save and come back. now you can release the TR. now the  datafile and cofile will be overwritten in OS level with same file name.

Cheers,
Hi Martin,

Thanks a lot for your queries. Actually I forgot to add this in the blog itself. Please proceed as follow.

Once you changed the TR into modifiable, you can change objects in the TR. you have to again release the task and TR.However, once we changed the released TR into modifiable, you can’t release the TR again and you will be getting an error “Request <Request ID> has the invalid attribute EXPTIMESTAMP”

you have to double click on the TR, navigate to the properties tab. enter into edit mode. you can see “Attribute” column in the screen.
Select the row “EXPORT_TIMESTAMP” and delete that row. save and come back. now you can release the TR. now the  datafile and cofile will be overwritten in OS level with same file name.

How to Call DLL Functions Inside ABAP

"-Begin-----------------------------------------------------------------
  Program zCallDLL.

    "-TypePools---------------------------------------------------------
      Type-Pools OLE2 .

    "-Constants---------------------------------------------------------
      Constants CrLf(2) Type c Value %_CR_LF.
      Constants OUTPUT_CONSOLE Type i Value 0.
      Constants OUTPUT_WINDOW Type i Value 1.
      Constants OUTPUT_BUFFER Type i Value 2.

    "-Variables---------------------------------------------------------
      Data PS Type OLE2_OBJECT.
      Data Result Type i Value 0.
      Data strResult Type String Value ''.
      Data tabResult Type Table Of String.
      Data PSCode Type String Value ''.

    "-Macros------------------------------------------------------------
      Define _.
        Concatenate PSCode &1 CrLf Into PSCode.
      End-Of-Definition.

    "-Main--------------------------------------------------------------
      Create Object PS 'SAPIEN.ActiveXPoSH'.
      If sy-subrc = 0 And PS-Handle <> 0 And PS-Type = 'OLE2'.

        Call Method Of PS 'Init' = Result Exporting #1 = 0.
        If Result = 0.

          Call Method Of PS 'IsPowerShellInstalled' = Result.
          If Result <> 0.
            Set Property Of PS 'OutputMode' = OUTPUT_BUFFER.

_ '$sig = @"'.
_ '[DllImport("User32.dll")]'.
_ 'public static extern int MessageBoxA(int hWnd, String Text, String Caption, int Type);'.
_ '"@;'.
_ '$DLL_User32 = Add-Type PBexpMsgBox -MemberDefinition $sig -PassThru'.
_ '$DLL_User32::MessageBoxA(0, "Hello World", "From WinAPI", 0);'.

            Call Method Of PS 'Execute' Exporting
              #1 = PSCode.

            Call Method Of PS 'OutputString' = strResult.

            Split strResult At cl_abap_char_utilities=>cr_lf
              Into Table tabResult.
            Loop At tabResult Into strResult.
              Write: / strResult.
            EndLoop.

          EndIf.

        EndIf.

        Free Object PS.

      EndIf.

"-End-------------------------------------------------------------------

SAP command field entries

/nxxxx - Call a transaction in the same session (window)
/*xxxx - Call transaction in the same session (window), whereby
  the initial screen is skipped.
/oxxxx - Call transaction in an additional session
/n     - To end the current transaction (Caution: Unsaved changes
  are lost without warning)
/i     - To delete the current session
/o     - To generate a session list
/ns000 - To end the current transaction and return to the starting
  menu
/nend  - To log off from the system
/nex   - To log off from the system without a confirmation prompt
  (Caution: Changes that were not saved are lost without
  warning)

/h   - Start the Debugger
/hs  - Start System Debugging
/ha  - Start Debugging but without screen handling

Key:
xxxx = transaction code

Sample ABAP Program to EXPORT or IMPORT internal table TO or FROM ABAP Memory

*second program to store data to  memory

REPORT  ZII_MEMORIES01.

START-OF-SELECTION.

SELECT *  FROM ZII_TCURT INTO TABLE CURR_TAB.

EXPORT CURR_TAB TO MEMORY ID 'CTAB'.

SUBMIT ZII_MEMORIES02 AND RETURN.

MESSAGE S036(ZII_MC01). 

 

 

 

*second program to retrive data from memory

 

REPORT  ZII_MEMORIES02.

DATA: CURR_TB TYPE STANDARD TABLE OF ZII_TCURT WITH HEADER LINE.

START-OF-SELECTION.

IMPORT CURR_TAB TO CURR_TB FROM MEMORY ID 'CTAB'.

LOOP AT CURR_TB.

 WRITE:/5(4) SY-TABIX, CURR_TB-WAERS, CURR_TB-LTEXT.

ENDLOOP.

Job table

tbtco
*&---------------------------------------------------------------------*
*& Report  ZUTIL_RELEASE_JOB
*&
*&---------------------------------------------------------------------*
* Identification
*   Technical Object(s)   : Program  -->  ZUTIL_RELEASE_JOB.
*   Title                 : Utility program that releases the next job in a set of spawned jobs
*   Description           : Utility program to release batch jobs
*   Technical Consultant  : Anil Vithal
*   Solutions Architect   : Don Chamberland
*   Functional Consultant : Manish Govil
*   Creation Date         : 26.07.2017
*   Project/Ticket        : BREWS
*---------------------------------------------------------------------*
* 26.07.2017    AVITHAL      BREWS Project – Realization
*---------------------------------------------------------------------*
* 28.02.2018    RGILMORE     Adjusted to ensure older job is released first
*                            Covered under defect 327 TRANSPORT:ED1K906519
*----------------------------------------------------------------------*

REPORT  ZUTIL_RELEASE_JOB.

PARAMETERS:
  p_job LIKE tbtcm-jobname OBLIGATORY.

data:
  gv_job type string. " LIKE tbtcm-jobname.

START-OF-SELECTION.
  perform f_check_input.
  perform f_release_job .

*&---------------------------------------------------------------------*
*&      Form  F_CHECK_INPUT
*&---------------------------------------------------------------------*
form F_CHECK_INPUT .
  data:
     lv_len type i,
     lv_char.

  lv_len = strlen( p_job ) - 1.
  lv_char =  p_job+lv_len(1).
  if  lv_char ne '%'.
    CONCATENATE p_job '%' into gv_job.
  endif.
endform.                    " F_CHECK_INPUT


*&---------------------------------------------------------------------*
*&      Form  F_RELEASE_JOB
*&---------------------------------------------------------------------*
*      release the next job
*----------------------------------------------------------------------*
FORM f_release_job .

  DATA:

    lv_date    TYPE dats,
    lv_tbtcstrt TYPE tbtcstrt,
    lt_new_steplist TYPE TABLE OF  tbtcstep,
    lv_rand     LIKE qf00-ran_int,
    BEGIN OF ls_tbtco,
      jobname   TYPE tbtco-jobname,
      jobcount  TYPE tbtco-jobcount,
      SDLSTRTDT TYPE BTCSDATE,   "new defect 327  RGILMORE
      SDLSTRTTM TYPE BTCSTiME,   "new defect 327  RGILMORE
    END OF ls_tbtco,
    lt_tbtco LIKE TABLE OF ls_tbtco.


  SELECT jobname jobcount SDLSTRTDT SDLSTRTTM FROM tbtco
    INTO TABLE lt_tbtco UP TO 10 ROWS
   WHERE jobname LIKE gv_job
     AND status    = 'P'
    order by SDLSTRTDT ascending SDLSTRTTM ascending.
*   added order by RE: defect 327.  RGILMORE

  IF  sy-subrc NE 0.   " NO MORE JOBS
    EXIT.
  ENDIF.

* Added sort order re defect 327. RGILMORE
  SORT lt_tbtco by SDLSTRTDT ascending SDLSTRTTM ascending.  "we want to hit the oldest job first via planned start date.

  LOOP AT lt_tbtco INTO ls_tbtco.
*   more jobs found - release one
    CALL FUNCTION 'BP_JOB_RELEASE'
      EXPORTING
        jobname                           = ls_tbtco-jobname
        jobcount                          = ls_tbtco-jobcount
*        CHANGING
*         RET                               =
      EXCEPTIONS
       missing_jobname                   = 1
       missing_jobcount                  = 2
       missing_start_date                = 3
       status_not_scheduled              = 4
       cant_enq_job                      = 5
       cant_start_job_immediately        = 6
       no_privilege_to_release_job       = 7
       cant_release_job                  = 8
       job_not_exist                     = 9
       job_have_no_steps                 = 10
       error_job_modify                  = 11
       OTHERS                            = 12.

    IF  sy-subrc EQ 0.  " success
      EXIT.
    ENDIF.

  ENDLOOP.


ENDFORM.                    " F_RELEASE_JOB

AL11

AL11

Nested Loop

*&---------------------------------------------------------------------*
*& Report  ZNESTED_LOOPING
*&
*&---------------------------------------------------------------------*
*& ABAP Sample Code
*& Performance in nested looping
*&
*& Mauricio Lauffer
*& http://www.linkedin.com/in/mauriciolauffer
*&
*& This sample explains how to use nested looping with performance
*&
*&---------------------------------------------------------------------*

REPORT znested_looping.


DATA:
  gt_bkpf TYPE STANDARD TABLE OF bkpf,
  gt_bseg TYPE STANDARD TABLE OF bseg.

FIELD-SYMBOLS:
  <gs_bkpf> TYPE bkpf,
  <gs_bseg> TYPE bseg.


"Select header
SELECT * UP TO 500 ROWS
  FROM bkpf
  INTO TABLE gt_bkpf.
IF sy-subrc <> 0.
  RETURN.
ENDIF.

"Select items
SELECT *
  FROM bseg
  INTO TABLE gt_bseg
  FOR ALL ENTRIES IN gt_bkpf
  WHERE bukrs = gt_bkpf-bukrs
    AND belnr = gt_bkpf-belnr
    AND gjahr = gt_bkpf-gjahr.

"Looping into header
LOOP AT gt_bkpf ASSIGNING <gs_bkpf>.
  "Get index (sy-tabix) for the first occurrence
  "You must guarantee that the table is sorted by the keys used in BINARY SEARCH
  READ TABLE gt_bseg TRANSPORTING NO FIELDS
       WITH KEY bukrs = <gs_bkpf>-bukrs
                belnr = <gs_bkpf>-belnr
                gjahr = <gs_bkpf>-gjahr
       BINARY SEARCH.
  CHECK sy-subrc = 0.

  "Looping into items from index which we got before
  LOOP AT gt_bseg ASSIGNING <gs_bseg> FROM sy-tabix.
    "Check the table key, if it has changed, leave this looping
    IF <gs_bkpf>-bukrs <> <gs_bseg>-bukrs
       OR <gs_bkpf>-belnr <> <gs_bseg>-belnr
       OR <gs_bkpf>-gjahr <> <gs_bseg>-gjahr.
      EXIT.
    ENDIF.

    "Do stuff...
  ENDLOOP.
ENDLOOP.