PO Output Determination Plant in ABAP Routine

Dear Experts,
I would like to get PO Item's Plant in abap customized output condition routine to control output message type, I noticed that KOMPBEA structure for item detail is not polulated and I had search the issue on SDN, seems no resolution... I read sap note 457497 as well, it mention that it is not possible to get item level detail also...
Any idea or workaround if I insist need to check item level while PO creating (ME21N).
Thanks in advance, your help is very much appreciated.
Regards,
Weng

Thanks Narayan.
It goes into the code for the requirement that I created to check for Plant and here is the code... But the structure KOMPBEA does not get populated with any values. Is there some other structure I can use to check the value for PLANT?
FORM KOBED_979.
*{   INSERT         TSTK941598                                        1
IF KOMPBEA-WERKS = 'T300'.
    SY-SUBRC = 0.
ELSE.
    SY-SUBRC = 4.
    EXIT.
ENDIF.
*}   INSERT
ENDFORM.
FORM KOBEV_979.
*{   INSERT         TSTK941598                                        1
PERFORM KOBED_979.
*}   INSERT
ENDFORM.
Regards,
Sneha

Similar Messages

Purchase Output determination Plant wise

Hi Experts,
Purchase Order Output determination is configured and we are successful to print. As we have 5 Plants, Every plant has a different Printer, and the default printer for other plants needs to be maintained.
We can maintain one Output device in communication tab, how can we maintain default printer for each plant to print only Purchase Order?
Example :
For Plant 1000 the printer is ZMM1
For Plant 2000 the printer is ZMM2
For Plant 3000 the printer is ZMM3
Kindly suggest your valuable inputs on this.
Best Regards
Javeed Ahamed

Hi Jurgen Master,
Kindly assist me with some more clarification.
Request you to assist me with the process for creation of Acess Sequence and its corresponding assignment.
Best Regards
Javeed Ahamed

Output determination routines

Hi,
I have an enhancement to develop output determination routines for the Output types in the Shipment document to trigger outbound interface to the Freight Forwarder based on the Shipment statuses.
Need to develop 2 routines say 950,951.
SD Shipment :
Output Type      Application      Routine Number
ZE01                           V7                              9XX
ZE02                            V7                              9XX
Routine for ZE01.
For the Shipment document number in the table VTTK (VTTK-TKNUM),check status VTTK-STTRG = 1 (Planning completed) then the Output will be triggered.
Routine for ZE02.
For the Shipment document in the table VTTK table check the status in VTTK-STRRG = 4 (Loading End) then issue the output.
I have created the routines and wrote the code for ZE01 like below.
FORM KOBED_984.
*if status of vttk-sttrg(Overall transportation status) is 1,(Planning completed) then outputtype is triggered.
IF VTTK-STTRG = 1.
SY-SUBRC = 0.
ELSE.
   SY-SUBRC = 4.
ENDIF.
ENDFORM.
This will work fine.?Or I need to consider the shipment document number anywhere.?NAST-OBJECTKEY will hold the document number.?i need to loop it.?or just the sy-subrc check is only required..?
Kindly help..
/Ranjith

Hi,
If you really want to be 100% sure that your requirements are rechecked before output, you need to use your own entry module when processing NASt output
See e.G. in TNAPR for your output type which print program/ form entry is used and replace it by your own entry module : Then you can check your own rules again and cancel before doing the actual output( i.e. don't call the 'processing' form )
( contra : you need make a copy of standard print program )
Alternatively, you could check e.g. the userexits that are triggered when reading the document data to be printed and set the correct return code ( r.g. retcode = 4 when your validations are not met ). This will stop processing also. ( e.g. GET_DATA_USEREXIT )
The correct names of the variables etc..depend on the print program that you are actually using .
( pro : Could maybe be done without copying standard print program )
Is it still standard print program ?
rgds
Dirk

PO Output determination using Plant as a condition

Hi All,
I want to use PLANT (werks) as a condition in PO output determination. How do I do that?
Basically, I want to be able to send ORDERS IDoc only when the Plant is a certain value. Where can I check the plant information before sending the output. I have tried to add plant in a condition table and then in the access sequence which is referenced in the output type. I have created a condition record for this condition table with PLANT also.
But for some reason when I save the PO it does not create a output message (ORDERS IDoc). If I use any other PO header field (like purch org or purch gp) in the condition it works and generates the ORDERS IDoc.
Any help would be greatly appreciated.
Thanks,
Sneha

Thanks Narayan.
It goes into the code for the requirement that I created to check for Plant and here is the code... But the structure KOMPBEA does not get populated with any values. Is there some other structure I can use to check the value for PLANT?
FORM KOBED_979.
*{   INSERT         TSTK941598                                        1
IF KOMPBEA-WERKS = 'T300'.
    SY-SUBRC = 0.
ELSE.
    SY-SUBRC = 4.
    EXIT.
ENDIF.
*}   INSERT
ENDFORM.
FORM KOBEV_979.
*{   INSERT         TSTK941598                                        1
PERFORM KOBED_979.
*}   INSERT
ENDFORM.
Regards,
Sneha

Output determination.( Routine)

Hi,
We are having a new order type.
We need to check few things before the output is determined.
I will just elaborate here.
Spro ->SD -> Basic Functions -> output control -> Maintain output determination for sales docs -> Maintain output determination procedure.
We get diff procudures.
We take a order output procudure and go to the control data.
In the requirement we have requirement starting from 900.
If we do a F4 on the procudure and go to source text we get the program where i can do few checks before the output is determined.
How can i write a new routine number ?
Pls advise.
Rohita.

Let me elaborate a more.
I am having a output type z02.
This needs to defaulted at the creation of the sales orders based on some conditions.
I have created a routine say 960 in vofm.
I am putting my custom code in the include which got created.When i create the order it is not breakining at the routine which is created.
Can any one pls advise why it is not breaking at the routine.

Output determination ----Urgent

Hi , I got a problem regarding Output determination in SD.
There is credit memo , created based on an invoice. When iam taking the "Print preview " at the header level of the credit memo, " the Reference no./Date "
is not showing anything.
When Iam checking the "Edit" button at the header level and then clicking on the "Processing Log", it is showing the following information:
    1. Object 0062000080
     2. Output type: Order Confirmation
     3. Processing log for program RVADOR01 routine ENTRY
     4. Appl. V1 - Problem during data retrieval -
         Table/structure   VBAK
     5. Window TITLE is not defined for form RVORDER01
     6. Element HEADER_DATA window MAIN is not defined
        for form RVORDER01
     7. Element HEADER_TEXT window MAIN is not defined for
         form RVORDER01
So, plz help me resolve this issue . What is the error and how to resolve this error?? Its an urgent case
Thanks with regards
Sourav Bhaumik

Dear Sourav,
          Chect the output type program RVADOR01 with the help of the ABAPer then debug the program then you can come to know what is the exact problem.
-->Before you Check the output determination assignment to the Creditmemo and output type assignment.
I hope it will help you
Regards,
Murali.
Edited by: Murali Mohan.T on Mar 31, 2008 8:34 AM

Line Item fields for output determination?

Hi Gurus,
we are having this dilemma. we want to create an output type for Purchas Orders which will be automatically triggered thru condition records. however, the criteria should include PLANT and MATERIAL GROUP which we all know as part of Line Item Details.
our problem now is that when the output types are created, our output is not created because the PLANT and MATERIAL GROUP criteria is not satisfied. it is empty.
is there a way to fix this? i'm thinking maybe some abap code or badi to force the value to the kompbea structure can do the trick (as the criteria came from this) but we have tried this and the kompbea field does not get populated.
any ideas? abap fix and configuration is most welcome. <removed by moderator>
thanks.
Edited by: Thomas Zloch on Nov 22, 2010 5:12 PM - please do not offer ..., read rules of engagement

Dear Guru's,
we just facing the already discussed issue that a PO within PLANT from PO-item-level should be part of the PO-output determination. Which userexits have to manipulated to get field PLANT into structure KOMKBEA_FILL especially when PO is still not saved (NO EKKO/EKPO information available) but message is already determined with status "NOT PROCESSED"???
Thanks for an answer.
Regards,
Bernd

Adobe Forms in Output Determination

We're looking at using an Adobe form to replace an existing SAPSCRIPT form in Output determination.
From SPRO, under the processing routines of the output type I can see a selection where a PDF form can be supplied.
I haven't done any detailed exploration yet.
A few questions:
>>Is there anything documented that explains how to use a PDF form created within the ABAP workbench as an output in output determination.
>>Should the processing program routine be used to call and populate data within the Adobe form?
Regards,
Lavaughn

Hi,
Did you check in transaction SFP what are the form available in your system ?
Also , check in the standard print program if it has been adapt to use Adobe Forms instead of smartforms because it's not the same FM used .
Regards

Vendor partner function is overriding my output determination for PO email

I'm trying to get a PO emailed to the user who created the PO based on purchasing group. I configured output determination so that a message is correctly getting generated -- in MN05 I've got the purchasing group tied to the VU (user responsible) partner function which specifies the SAP User.
My issue is that the PO is using the vendor (VN) partner function to pull in the vendor address which needs to appear on the PO form. So the system is always looking to the vendor's email for the output instead of my output determination message. Is there any way to disable this yet still use the vendor address for the PO form?
Note that everything is configured properly and I am receiving PO email based on the email in the vendor master. I'm trying to do the same using output determination instead.
Thanks, Vlad

Hi,
1.) got to transaction NACT, Select the Output type; say NEU, and then Select the Partner Function. You can change it as per your requirement for Ordering address, Vendor, Delivering plant.
2.) Yes you can use Vendor's address in the PO Form. For that you would need assistance from ABAP.
Prashant Rathore,

Output determination problem

Dear Pavan,
How do i stop RD00 output type to trigger in the billing document if an SAP Accounting document has been created.
My requirement is to stop RD00 from firing if the accounting document is not generated in the billing document.
I tried out with routine 62 in the billing output determination procedure but it seems to be not working.
I think i should use some logic into in the 62 routine and obtain this functionality?
Now my questions is what logic should i use which would stop RD00 from firing output when the accounting document is not released in the billing.
Or suggest me how do i have to do it.
Thanks in advance,
Praveen

You will have to use user exit for this, I dont have have the name of user exit but logic will be like this,
When billing doucument is saved accounting is generated, and status is updated in VBRK table.
In VBRK field RFBSK is there i.e posting status.
Just put a check at the time of saving the billing document , if the satus is not posted give error message that output cannot be issued
Take help of abaper to stop issuing of the output.
Thanks and Regards

Purchase Order and GR document Output Determination and creating own logo o

Can anyone let me know the process of output determination of PO and GR documents.
Also let me know the way to incorporate my own logo on the documents

Hi sudip
For the logo on documents, you have to take help of ABAP ppl.
Output of Purchase Order
1. Condition Table
SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
Select:
Purchasing Doc. Type,
Purch. Organization,
Vendor
2. Access Sequences
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
3. Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
*4. Message Determination Schemas*
4.1. Message Determination Schemas
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
4.2. Assign Schema to Purchase Order
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
5. Partner Roles per Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
6. Condition Record
Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type.
Output of GR
After setting table, access sequence and output type for GR,run MB02 transaction, enter material document number. Double click one line item and select messages. Separate screen will be opened to configure outputs. Give the required fields and save the document.
Now Run MB90, you can take printout. Output Type: WE03 or WE01 or WE02

ABAP Routine in UR Help

Hi Friends
We are on BI7 and ECC6.
We have to get the quantities into BI from ECC for that we are using one field from 2lis_11_vaitm. But we want to count the quantity only when material is a complete package all other values should be 0. Packages are described in the material as for example DMS PACKAGE , DST PACKAGE , DTTS PACKAGE DTTTT PACKAGE.
Now My thinking is ,Inorder to do that we have to use the offsets in ABAP routine. But the first few letters are not 3 / 4 fixed it may be 3, 4, 5 or 6 letters the PACKAGE will start from the next word..
Can any one help me how to write the ABAP logic to get the offset for last 11 letters ?
regards

F2 & F3 TYPE I.
F1 = 'DTTS PACKAGE' (F1 contains the value)
F2 = LENGTH(F1) (F2 determines the length of the field)
OR
F2 = STRLEN(F1)
F3 = F2 - 11 (F3 determines the difference)
F4 = F1+F3(11) (F4 picks up value based on offset)
*Not sure if variables are accepted for offsets.

No output determined for GR slip

Hi Experts,
Need your help to analyze a situation.
My system is not able to determine a output condition record for a material document for GR. The system ends up in a error "The system could not create any outputs". Although the system immediately generates a output when the printer name is filled in the condition records.
Settings currently done in the system:-
- Proper customizing exist in the system for output detrmination for Inventory management.
- Print parameters for WE01(individual slip) is set to S "User parameters".
- Condition record maintained for WE01 with dispatch time 4 for a "print" output. The printer field is kept blank.
- User parameter NDR not Set. The check box XNAPR is checked manually.
- A printer is set in the User parameters -
>Defaults -
Output device -
ML0001(physical printer).
OSS notes already checked:-
446041 (sympton 2 applies, but it doesnot help).
426554 (all settings done as per the checklist)
The system should act as below but unfortunately it doesn't.
The system checks whether a printer has been specified in the condition record. If so, it is used. If not, it checks the message type to see whether a print parameter has been set. If no parameter has been set, no message is generated. If a parameter has been set, a printer is sought in accordance with this parameter. If a printer is found, it is used to output the message. If not, no message is generated.
Please help me with your expertise.
Regards
Raj
Edited by: RajKiran Mohanty on Mar 8, 2012 4:31 AM

Hi,
I am not sure but check this
sap 426554: check lists for output determination and printer determination for goods movements
Checklist 2: Check printer determination Customizing
1. Which printer do you want to use?
Printer: _____
Is the printer defined in the MM-IM Customizing? (Customizing MM-IM > Print Control > General Settings > Printer setting)
Entry exists: _ yes / _ no
2. Does the condition record have a fixed printer (see question 6 of checklist 1)? (Customizing MM-IM > Output Determination > Maintain Conditions > Communication). Note that it does not usually make sense to define a printer in the condition record otherwise all messages are printed with this printer.
Printer in condition record: _ yes: Printer ______ / _ no
3. Which print parameter does the output type have? (Customizing MM-IM > Output Determination > Output Types)
_ Plant/storage location (7)
_ Plant/storage location/user group (9)
_ User (combination of output type/user name) (U)
_ User parameters (printer from user master record) (S)
a) Printer determination according to plant/storage location (7)
Which plant/storage location do you use?
Plant: ____ Storage location: ____
If the purchase order has an account assignment, the storage location is initial.
Is there an entry for the printer determination with the above combination? (Customizing MM-IM > Output Determination > Printer Determination)
Entry exists: _ yes / _ no
b) Printer determination according to plant/storage location/user group (9)
Which plant/storage location do you use?
Plant: ____ Storage location: ____
If the purchase order has an account assignment, the storage location is initial.
With which user is the material document posted? (See question 7 of checklist 1)
User:________________
Which value does parameter ND9 have for this user (display user master record > parameters)
Parameter ND9 (user group): __________________
Is there an entry for the printer determination with the above combination? (Customizing MM-IM > Output Determination > Printer Determination)
Entry exists: _ yes / _ no
c) Printer determination according to user (output type/user name) (U)
With which user is the material document posted? (See question 7 of checklist 1)
User:________________
Is there an entry for the printer determination with the above combination? (Customizing MM-IM > Output Determination > Printer Determination)
Entry exists: _ yes / _ no
Have you mark fixed indicator for printer?
Regards
Kailas Ugale
Edited by: kailasugale on Mar 8, 2012 2:14 PM
Edited by: kailasugale on Mar 8, 2012 2:16 PM

Delete Overlapping Requests - by Filename via ABAP Routine

Hi SDN Community
Do you know if it is possible to set the delete overlapping request parameters to recoginse the file name, and remove it via the derivation of the file name via an ABAP Routine.
I am using an ABAP routine to derive the flat flat file upon loading, but do not know the syntax, or if it is possible to set this equivalent code into the delete overlapping request Routine area
(The code basically derives the first day of the calendar week, for previous weeks in the Do n times Loop
Thank you.
Simon
DATA: ld_CWEEK         TYPE scal-week,
      ld_DATE          TYPE SY-DATUM,
      ld_DATE1         TYPE SY-DATUM,
      lc_DIRECTORY(30) TYPE c,
      ln_YYYY(4)       TYPE n,
      ln_WW(2)         TYPE n.
*Derive week from sy-datum
ld_date = SY-DATUM.
Determine the calendar week from the entered calendar date
CALL FUNCTION 'DATE_GET_WEEK'
    EXPORTING
      date           = ld_date
    IMPORTING
      week          = ld_cweek
    EXCEPTIONS
      date_invalid = 1
      OTHERS        = 2.
Get the First day of the week
        CALL FUNCTION 'WEEK_GET_FIRST_DAY'
          EXPORTING
            week         = ld_CWEEK
          IMPORTING
            date         = ld_DATE1
          EXCEPTIONS
            week_invalid = 1
            OTHERS       = 2.
Need to find the previous calendar week and reconvert to the first
day in order to accomodate weeks less than 7 days
Get the last day of the current calendar week - 2
    DO 2 TIMES.
        ld_DATE1 = ld_DATE1 - 1.
Determine the calendar week from the last day of the previous week
        CALL FUNCTION 'DATE_GET_WEEK'
          EXPORTING
            date         = ld_DATE1
          IMPORTING
            week         = ld_CWEEK
          EXCEPTIONS
            date_invalid = 1
            OTHERS       = 2.
Get the First day of the week
          CALL FUNCTION 'WEEK_GET_FIRST_DAY'
            EXPORTING
              week         = ld_CWEEK
            IMPORTING
              date         = ld_DATE1
            EXCEPTIONS
              week_invalid = 1
              OTHERS       = 2.
    ENDDO.
*ln_YYYY = ld_CWEEK(4).
ln_YYYY = ld_DATE1(4).
ln_WW = ld_CWEEK+4(2).
*DIRECTORY represnts path where file is stored .
lc_DIRECTORY = '/interfaces/EDW/data/CSM/'.
CONCATENATE lc_DIRECTORY
ld_date '_WEEK' ln_WW '_c1_pri_' ln_YYYY '.csv' into p_filename.
'MIC_NT_' ld_date1 '_' ln_YYYY '.csv' into p_filename.

Thank you for your response Debanshu
However, i could not find this process type in the process chain area.
Is this where you meant, can you please give me more detailed steps including long syntax of names of process types
We are on BW 3.50
i assumed the filename had to be constructed via abap according to some of the sdn replies i've searched through.
Thank you.
Simon

ABAP Routine for 0FISCPER slect options in InfoPackage

Hi,
I am trying to write an ABAP Routine for 0FISCPER as select options (range) dynamically.
Ex:
0FISCPER selection for this year as 001.2008 to 012.2008
0FISCPER selection for next year as 001.2009 to 012.2009.
Now we are changing InfoPackage every year manually, so I need to write a routine for 0FISCPER in InfoPackage to handle dynamically every year
Thanks,
SK.

Hi
write an ABAP routine to get that value..But are you getting any planned data(why you want till end of the year...till infopackage runs is o.k i think, if you don't have planned data)...Any way you can check the below code, which can be useful...
You can see the below code at->your infopackage selections>Ty-->choose variable type as 6 and enter any ABAP routine name( to create) and then there is a button on the application tool bar called 'routine info'..this give you the following information...
Definition
You can define complex selections for InfoPackages and control the automatic deletion of requests from InfoCubes in the scheduler, by using routines.
Routines are processing blocks in ABAP programs that consist of a pre-defined data declaration section and an ABAP subroutine (form routine). In the subroutine you can use all of the ABAP programming functions.
You can use the following routines for making selections in InfoPackages:
1. Selection routines for fields, on the Data Selection tab page
2. Selection routines for file names, on the External Data tab page
3. Selection Routines for selecting the from and to dates for time-dependent data, on tab page Update
4. Selection routines for determining old requests to be deleted after successfully loading a new request, on the Data Target tab page
Program frame:
After you have called up the Editor for routine maintenance, you get the following program frame:
1. Selection routines for fields, on tab page Data Selection:
program conversion_routine.
'$*$ begin of global - insert your declaration only below this line -
TABLES: ...
DATA:   ...
$$ end of global - insert your declaration only before this line    -
FORM COMPUTE_<Fieldname>
tables l_t_range structure rssdlrange
changing p_subrc like sy-subrc.
$$ begin of routine - insert your code only below this line       -
data: l_idx like sy-tabix.
        read table l_t_range with key
             fieldname = <Fieldname>.
        l_idx = sy-tabix.
        modify l_t_range index l_idx.
        p_subrc = 0.
$$ end of routine - insert your code only before this line       -
ENDFORM.
2. Selection routines for file names, on tabstrip External Data:
FORM compute_flat_file_filename
     changing p_filename like rsldpsel-filename
          p_subrc like sy-subrc.
$$ begin of routine - insert your code only below this line-
          p_filename =
          p_subrc = 0.
$$ end of routine - insert your code only before this line-
ENDFORM.
3. Selection routines for selecting the from and to date for time-dependent data, on tabstrip Update:
form compute_time_dependent_dates
     changing p_datefrom type d
              p_dateto   type d
           p_subrc like sy-subrc.
$$ begin of routine - insert your code only below this line-
          p_datefrom =
          p_dateto   =
          p_subrc = 0.
$$ end of routine - insert your code only before this line-
ENDFORM.
4. Routines for determining the old requests to be deleted after successfully loading a new request, on tab page Data Targets:
form compute_<InfoCube-Name>
tables l_t_request_to_delete structure rsreqdelstruc
using l_request like rsreqdone-rnr
changing p_subrc like sy-subrc.
*Insert Source Code to decide if requests should be deleted.
*All Requests in table l_t_request_to_delete will be deleted
*from Infocube <InfoCube-Name>.
*Add new requests if you want to delete more (from this cube).
*Remove requests you did not want to be deleted.
$$ begin of routine - insert your code only below this line-
     loop at l_t_request_to_delete.
     endloop.
     clear p_subrc.
$$ end of routine - insert your code only before this line-
ENDFORM.
Note:
Those fields flagged with <...> are dependent on the selection fields and are filled automatically by the system when you call up the Editor.
Procedure
Make the following entries:
1. Between $$ begin of global ... and $$ end of global ... you can define data declarations. These are the declaration sections for the local data in the routine. This data is only visible in the routines.
2. The subroutines begin with FORM and end with ENDFORM.
The subroutines for the particular routines are:
Selection routines for fields on tab page Data Selection: FORM COMPUTE_<Field name>
Selection routines for file names on tab page External Data : FORM compute_flat_file_filename
Selection routines for selecting the from and to dates for time-dependent data on tab page Update: FORM compute_time_dependent_dates
Routines for determining old requests to be deleted after successfully loading a new request on tab page Data Target: FORM COMPUTE_<InfoCube-Name>
The subprograms have the following parameters:
Subprogram FORM COMPUTE_<Field name>:
l_t_range
In the table l_t_range the routines for all selection fields that are filled, or have a routine, are made available.
The routines are executed in the scheduler last of all and therefore, you can change all the selections that you have carried out previously.
p_subrc
Using the variable p_subrc you can report errors to the scheduler. p_subrc <> 0 signals an error and means the data request is terminated.
Subprogram FORM compute_flat_file_filename:
p_filename:
You give the name of the file that is to be loaded in parameter p_filename.
This is useful if your file name contains date dependencies that should be determined by sy-datum and calculated during runtime.
p_subrc
You can inform the scheduler of an error with variable p_subrc. p_subrc <> 0 signals an error and means that the data request is terminated.
Subprogram FORM compute_time_dependent_dates:
p_datefrom and p_dateto
Fill these parameters with the from and to dates for time-dependent master data and texts.
p_subrc
You can inform the scheduler about an error using variable >LS>p_subrc. p_subrc <> 0 signals an error and means the data request is terminated.
Subprogram FORM COMPUTE_<InfoCube-Name>:
l_t_request_to_delete
You give the request number of the request that is to be deleted in parameter l_t_request_to_delete. You can also delete requests from the table. These are then not deleted.
p_subrc
You can inform the scheduler about an error with the variable p_subrc. p_subrc signals an error and means the data request is terminated.
3. Insert your program code for the routines between $$ begin of routine ... and $$ end of routine ... so that the respective subprogram variables are supplied with the corresponding values.
4. Check the syntax of your routine with the Check function.
5. You can then transfer the routine with the Save function.
You end routine maintenance when you exit the Editor.
Hope it helps
Thanks,
Teja

PO Output Determination Plant in ABAP Routine

Similar Messages

Maybe you are looking for