Mass Variant for OBD creation+PGI

Posting this after some initial research on this with our developers.
We have a task at hand which we would like to do in mass but thereu2019s not really a consensus on whether it is possible
Creation of OBD and doing PGI for some (large) open sales orders by confirming the pick qty= ordered qty where materials = a, b, c and storage location = 2. I,e the attributes to be changed in mass are not for all line items but for those line items with specific materials and specific storage location and set the pick qty to 1 and do the PGI and hence save the OBD (VL02N)
Basically this is a slight deviation from standard wave job program as we are confirming the pick qty for selective lines that meet the unique combinations of Material and storage location and the pattern of that is random.
If someone has done such a task before, through some mass maintenance tools (without the need for deploying a program in production), pls. reply. If additional info is required, pls. let me know.
Also do share your ideas to accomplish this, even if you have not done it ditto before.
Even if we can do this using combination of multiple variants of mass maintenance and standard FM's pls. let me know, anything that can cirumvent the manual process that we are doing now.
Regards,

Sounds rather unusual to me, so I doubt there is a standard program. I would have to search for it just like you could.
You could try recording the steps for one such copy e.g. via SHDB and feed the variant names from an Excel sheet.
Thomas

Similar Messages

ALE Error + Mass deletion of variants for Reports

Hi,
I have two questions
1- is there any transaction in SAP, which delete the mass variants for reports for all users?
2- I am getting an error An Idoc without a message type was passed to the ALE layer.
I have already check file port is set up correctly and I am passing message type HROT_BRM.
This also happen in previous test, as user does not have the proper authorization, so I assign the authorization and ran it. It worked.
However, this time a user has the authorization and still the error messaging is coming. Am I missing something?
Waiting
Bye

There are some function modules like "KYVA_REPORT_VARIANTS_DELETE or get user variants "RM_GET_VARIANTS_4_REPORT_USER".
- is there any transaction in SAP, which delete the mass variants for reports for all users?
2- I am getting an error An Idoc without a message type was passed to the ALE layer.
I have already check file port is set up correctly and I am passing message type HROT_BRM.
This also happen in previous test, as user does not have the proper authorization, so I assign the authorization and ran it. It worked.
However, this time a user has the authorization and still the error messaging is coming. Am I missing something?

HOW TO Create variants for transaction MASS on LFA1 object?

hOW TO Create variants for transaction MASS on LFA1 object?
Edited by: cheppalliakr on Nov 10, 2011 1:09 PM
Moderator message: please do more research before asking, show what you have done yourself and provide more information when asking.
Edited by: Thomas Zloch on Nov 10, 2011 3:10 PM

Hi Oscar ,
You need to create optional date prompt variable in BW which fills your requirement .
Ex : If you require report should always run for 1st of the month to last of month .Then create Optional date variable in BW with interval .write customer exit ,
if from date is left blank it should take 1st of the month and if todate is left blank it should take last of the month .
when creating webi schedules , leave prompts as blank.

Problem in SHD0 about creation of Transaction Variant for VA02

Hi All,
My goal is to create a Transaction Variant for VA02 Variant that doesn't display the "Object Status" button under the page "Status" in the Header of Sales Orders.
To do so, I created a Transaction Variant in SHD0 (named ZTEST_VA02), the creation process creates the Screen Variants too, and i named them ZTEST_VA02_<dynpro_number>.
The Dynpro where I can found the button to hide is the SAPMV45A / 4305, so the Screen Variant Name is ZTEST_VA02_4305.
My problem is that If I test the single Screen Variant (ZTEST_VA02_4305) using the button in SHD0, I can see the whole transaction with my modify (the "Object Status" button is hidden), but testing the entire Transaction Variant ZTEST_VA02 I cannot see the modify and the Button is pretty visible.
I even tried to create a Transaction with Variant, in SE93, that launches the transaction VA02 with the variant ZTEST_VA02, and I tried to assign the Transaction Variant I created as a Standard Variant, in both cases the problem is that the modify doesn't appear to be applied.
For me this is a real mistery because If the Screen Variant is right (It works) I would expect to see that even the Transaction Variant is correct.
Does Anyone have (or have ever had) this problem?
Thank You very much for your attention.
Regards,
Claudio
PS: I forgot to mention that I'm working on SAP ECC 6.0
Edited by: Claudio Distrutti on Apr 4, 2008 11:47 AM

I too facing the similar problem when assigning the screen variant to transaction variant.
screen number where the 'Obj.Status' button is ' 4456
if executing the screen variant alone , it works perfectly,
once i assing to the transaction variant and test, the 'Obj.Status' button is visible.
does anyone got the solution?
Edited by: Thomas Paul jr on Oct 21, 2010 1:59 PM

Mass deletion of variants for Total Records

Hi there,
during tranings we create a lot of variants for the Total Records (UCWB->Analysis->Total Records->Save Variant). Is there a way to do a mass deletion of those variants?
The standard options of deleting variants only allows to delete one variant per selection.
We work with a SEM BCS EHP 4.
Thanks for all help,
Helge

Helge
you can do a mass deletion of variants.
First you will need to find the program name for the Totals Records. This can be found from the totals records screen when you click the Get Variant button. Across the top of the dialogue box you will see;
"Variant catelogue for program XXXXXXXXX".
Note this program ID.
Go to TCode SE38
Key in the program - make sure the Short description for the Program is "List of Totals Records"
Check the Variants checkbox
Click on Display
From the menu - go Variants > Catelogue
This should give a list of the variants for the Totals Records. If not then you must have the wrong program.
Click the button which has the picture of the rubbish bin with the words "Selection Criteria".
This will then allow you to put a check mark against all the variants you want deleted.
Click the button which has the picture of the rubbish bin with the word "Variant"
This will then mass delete your variants.
Regards

Delete Variants for Transaction MASS

Is it possible to delete multiple variants for transaction MASS?
I am aware variants can be deleted one by one using Goto... Variants... Delete. However, I would like to delete over 200 variants which are no longer required.
Surely there is a standard function? Deleting hundreds of variants one at a time is not an option. Contracting an ABAP programmer is not an option.
Thanks for your advice.

Hi G. Lakshmipathi,
Your suggestion to use BDC recording worked like a charm.
However, I am still surprised that there is no standard function.
Thanks for your help.
Regards,
Nathan

Creation of a Variant for FBL3N

Hi Gurus,
Actually, i want to create a variant for GL line item display with posting date range as last month's date range.
For eg. if i use that variant in october, it should pick posting date range from 01.09.08 to 30.09.08 and i use this variant in november, it should pick posting date range from 01.10.08 to 31.10.08.
Please help me in solving this issue.
Thank You

On the report's selection-screen:
1. Hit the SAVE button to create a variant
2. In the table 'Objects for Selection Screen':
               2.1. scroll to the row showing your input selection field (say posting date) and
               2.2. in column 'Selection Variable' of the respective row   select 'D'.
               2.3. in column 'Name of the Variable' of the respective row select 'Previous month'
Edited by: Prasad Kosuru on Nov 28, 2008 7:25 PM
Edited by: Prasad Kosuru on Nov 28, 2008 7:28 PM

OBD creation as soon as GR is done-third party order process

Hi Gurus,
*Below is my client scenario, need your expertise replies.
My client palces a PO to vendor in China to drop ship to end customer in China.This is purely standard thirdparty order process,But as soon as Vendor delivers the material to customer, we need to do virtual GR and need Auto delivery creation and PGI.
Is this possible to have Auto OBD creation as soon as GR is done?
I know through batch jobs we can do this, but do we have SAP standard functionality.
Appreciate your answers.
thanks
Vivek

Well that is possible via IDOC's. but for that you need to have XI system
let me throw some information
the moment GR is posted in your system it should trigger an IDOC which will go to XI system via an interface and from XI it will pick the values relevant for outbound delivery as in XI they can do value mapping and key mapping.
so from XI it will send a inbound IDOC carrying the outbound delivery details.

Dynamic Variant for Date Range

Making the Variant for Date or Date Range Dynamic in the Selection Screen of any Program.
There are actually many ways you can make the Variant for Dateu2019s Dynamic.
1.     Providing he Values in the Variant Variables.
2.     By creating the variables in the table TVARVC
3.     By Initializing the values in the program itself.
I saw many posts with respect to these and found that everyone has their own way of dealing. Even I wrote code in the program initialization to get this done.
Here in this post I am showing you the easiest option which is available in the Variant creation.
EX : If you want to execute the batch job based on a date range.
     SY-DATE u2013 60 days , that means always your program should execute the batch job based on System Date. And the variant should change accordingly.
Following are the step by stop to do that.
1. Select your program and select the Variant Radio button and then Click on Display.
2. It will pop up a screen with variant option below the program name.
3. Enter the Variant name and click on Create
4. You will see a screen, with the Attributes button.
5. Once you click on the Attributes button, it will take you a screen with selection option.
6. In my scenario my input is based on Calender Day, so select the Selection Variable for Calender Day: You will find 2 options T & D.
7. Select D: Dynamic date Calculation, then select the Name of Variable (input using f4). You can find many options.
8. Scroll down the Variant Attributes and select current date u2013 xxx, current date + yyy
9.Though it seems to be inactive, just double click on the row to provide the date range.
10. Just enter the value for xxx and yyy to get you dynamic range based on number of days
11. In my scenario I have to consider System Date u2013 60 days. 0 means current day.
12. Click on OK to check the range has been reflected or not. Then save the Variant and check the value by executing the program with saved Variant.
You can check the same in blog with all the screen shots attached but this thing is so easy you don't require screen shots.
Regards
Shankar Chintada

Hi Shankar,
It would be great if you can put this information in Wiki .
Pravender

Transaction Variant for Transaction FV60 (Parked AP Invoice)

Hi All:
I have been successful in creating a transaction variant for transaction code FV60 (Park AP Invoice). My objective was to get rid of the post and save as completed buttons on the FV60 screen. But when I simulate the document, the post and save as completed buttons appear again and I have been unsuccessful in getting rid of these and deactivating/hiding them.
Can anyone please help me or has anyone done this before?
you help is very appreciated
thanks
Brian

Hi you can hide the button as follows;
While doing SHDO Variant Creation , in the confirm screen entries dialog press Menu Functions button and in the dialog expand Function setting tree and select BU (POST) and press Deactivate button (or F2 key) then select PBBP(Save as completed) and press F2 again.
Now save the variant and activate it.
Now check the tcode, those two buttons will be hidden.
This will solve your problem.
Regards
Karthik D

Transaction Variant for VA01

Hi All,
I am able to create transaction variant for transaction code MM01, XD01 and XK01 successfully. But i am unable to create transaction variant for VA01.
And also some times i am getting error message "SAP Object SCV1(short text of variant) cannot be assigned to package ZXXX". Can you pls let me know why i am getting this error and why i am unable to create transaction variant for VA01 successfully.
Thanks,
Raju

Hi,
There is no difference in creation of the transaction variant for VA01/02. But the way it works is different. It works at order type level instead of t-code level. You have to create the variant in SHD0 and assign the same in order type customization.
Alternatively you can populate the field TVAK-VARIANT with the transaction variant name in MV45AFZZ subroutine USEREXIT_MOVE_FIELDS_TO_VBAK/USEREXIT_FIELD-MODIFY. With out this it wont work. Just try to change the TVAK-VARIANT value in debug mode and see if it works fine. Surpricingly it works fine if you individually execute the variant.
The error you mentioned might be because you might have given one of the screen variant name not starting with Z or Y.
Thanks,
Vinod.

Screen Variant for VA02

Hi,
I have a requirement according to which I need to make few fields of transaction VA02 as output only.
While we create a sales order using VA01, all fields should be writable but when we open the sales order in change mode(using VA02) fields Ship-to-party, Net-Value should not be editable whereas all others should be. I have created a transaction variant for VA02 and also activated it. But the changes are not getting reflected when I open a sales order using VA02.
Can any body help please. Thanks in advance.
Regards,
Dhiraj

HI
After Creation of Screen for reflecting changes you have to active screen variant
Screen Activation procedure:-
STEP1: T-code:SHD0 --> Enter transaction code: VA02
STEP2: Click on "Stanrad Variant" tab --> Again choose "Standard variants tab"
STEP3: Enter your variant name --> click on Active(Button)[it is in right side of inputfield name]
Appreciate points if it is useful.
Thanks & Regards
Sudheer Madisetty

To assign Screen Variant for VL02N to respective user.

Hi Experts,
I have created one Screen Variant for TCode VL02N. It is very well working if executing with SHD0.
Now, I want that, if any particular user say XYZ executes VL02N, then VL02N should be executed with the variant I created, for that user.
Plz. tell me what to do for this....any authorization object needs to create or is there any other way out.
Thanks in Advance.
Rgrds,
Rahul

Rahul,
Am not sure whether you can create user-group from SHD0.
just try to use these exit and do small code just like this:
is sy-uname = than perform.
Enhancement
VMDE0004                                Shipping Interface: Message SDPACK (Packing, Inbound
VMDE0003                                Shipping Interface: Message SDPICK (Picking, Inbound
VMDE0002                                Shipping Interface: Message PICKSD (Picking, Outboun
VMDE0001                                Shipping Interface: Error Handling - Inbound IDoc
V53W0001                                User exits for creating picking waves
V53C0002                                W&S: RWE enhancement - shipping material type/time s
V53C0001                                Rough workload calculation in time per item
V50S0001                                User Exits for Delivery Processing
V50R0004                                Calculation of Stock for POs for Shipping Due Date L
V50R0002                                Collective processing for delivery creation
V50R0001                                Collective processing for delivery creation
V50Q0001                                Delivery Monitor: User Exits for Filling Display Fie
V50PSTAT                                Delivery: Item Status Calculation
V02V0004                                User Exit for Staging Area Determination (Item)
V02V0003                                User exit for gate + matl staging area determination
V02V0002                                User exit for storage location determination
Amit.

URGENT- Update for picking confirmation & PGI

Hi Experts,
Is there any FM/BAPI to update delivery for both the picking confirmation & PGI.
I am trying to use WS_UPDATE_DELIVERY_2 but it is triggerring me an error at delivery positions.
If it is the correct FM used then plz forward me the parameters for the req.
Thank you,
Sangeetha

Check with below logic :
if flag = 'X'. Assume that flag = X means - PGI else delivery update.
Use FM - WS_DELIVERY_UPDATE
else.
Use FM : SD_DELIVERY_UPDATE_PICKING
endif.
Check the below code for ref PGI ..
REPORT ZWM_OVERWEIGHT_FIX no standard page heading
                           message-id zwm.
======================================================================
Program Name : ZWM_OVERWEIGHT_FIX                                    *
Description : Tool to fix Overweight in delivery line item,         *
               Used All Function module to cancel invoice ,          *
               Reverse the goods issue ,Update Delivery qty,Create *
               invoice                                               *
Author       : Seshu                                                 *
Date         : 05/08/2007                                            *
MODIFICATION HISTORY                                                 *
DATE    | AUTHOR   | CHANGE #   | DESCRIPTION OF MODIFICATION        *
--|||--
05/08/07| Seshu    | DEVK921979 | Initial                            *
D A T A - D E C L A R A T I O N     *******************
Tables
Tables : vbak,
         vbap,
         vbfa,
         likp,
         lips,
         vbrk,
         vbrp.
Internal Tables
data : i_lips like lips occurs 0 with header line,
       i_vbap like vbap occurs 0 with header line.
Variables
data : v_deliv like vbfa-vbelv,
       v_invoic like vbfa-vbelv.
Data Declaration Part for Post Goods Issue
DATA: l_vbeln LIKE likp-vbeln,
      l_vbkok LIKE vbkok,
      i_prot LIKE prott OCCURS 0 WITH HEADER LINE,
      ef_error_any_0 TYPE c,
      ef_error_in_item_deletion_0 TYPE c,
      ef_error_in_pod_update_0 TYPE c,
      ef_error_in_interface_0 TYPE c,
      ef_error_in_goods_issue_0 TYPE c,
      ef_error_in_final_check_0 TYPE c,
      d_return   LIKE bapireturn1.
Internal tables for BAPI Function Module
data : i_cret like BAPIRETURN1 occurs 0 with header line,
       i_csucess like BAPIVBRKSUCcESS occurs 0 with header line,
       i_ret2 like bapiret2 ,
       flag type c,
       i_mesg like mesg occurs 0 with header line.
Data Declaration for Invoice Creation
DATA: VBSK_I     LIKE VBSK.
data: d_success type c.
DATA: XKOMFK LIKE      KOMFK   OCCURS 0 WITH HEADER LINE,
      XKOMV LIKE      KOMV    OCCURS 0 WITH HEADER LINE,
      XTHEAD LIKE      THEADVB OCCURS 0 WITH HEADER LINE,
      XVBFS LIKE      VBFS    OCCURS 0 WITH HEADER LINE,
      XVBPA LIKE      VBPAVB OCCURS 0 WITH HEADER LINE,
      XVBRK LIKE      VBRKVB OCCURS 0 WITH HEADER LINE,
      XVBRP LIKE      VBRPVB OCCURS 0 WITH HEADER LINE,
      XVBSS LIKE      VBSS    OCCURS 0 WITH HEADER LINE,
      XKOMFKGN LIKE    KOMFKGN OCCURS 0 WITH HEADER LINE.
S E L E C T I O N - S C R E E N   ******************
Selection-screen
Selection-screen : begin of block blk with frame title text-001.
parameters : p_vbeln like vbak-vbeln obligatory.
selection-screen : end of block blk.
A T - S E L E C T I O N - S C R E E N ***************
Validation on Sales order
at selection-screen on p_vbeln.
Check the data on VBAK Table
select single vbeln from vbak into vbak-vbeln
                            where vbeln = p_vbeln.
if sy-subrc ne 0.
    message e006 with p_vbeln.
endif.
S T A R T - O F - S E L E C T I O N *******************
Start-of-selection.
break sreddy.
Get the Invoice Number corresponding Sales Order Number
perform get_invoice.
Step 1.
Cancel the Invoice - Transaction VF11
perform cancel_invoice.
Reverse the goods issue
perform reverse_goodsissue.
Get the Order and Delivery Items
perform get_sales_deliv.
Delivery Change
perform Delivery_change.
Create Invoice document
perform invoice_create.
E N D - O F - S E L E C T I O N *******************
end-of-selection.
if flag = 'X'.
message i012 with p_vbeln.
endif.
*&      Form get_invoice
      Get Invoice Number
FORM get_invoice.
Clear Variables
clear : v_deliv,
          v_invoic,
          flag.
Get the Delivery Number First
select single vbeln from vbfa into v_deliv
                           where vbelv = p_vbeln
                           and   vbtyp_n = 'J'.
if sy-subrc ne 0.
    message i004 with p_vbeln.
    stop.
endif.
Get the Invoice Number
select single vbeln from vbfa into v_invoic
                           where vbelv = p_vbeln
                           and   vbtyp_n = 'M'.
if sy-subrc ne 0.
    message i003 with p_vbeln.
    stop.
endif.
ENDFORM.                    " get_invoice
*&      Form cancel_invoice
      Cancel the Invoice
FORM cancel_invoice.
clear : i_ret2,
          i_cret,
          i_csucess.
refresh : i_cret,
            i_csucess.
CALL FUNCTION 'BAPI_BILLINGDOC_CANCEL1'
    EXPORTING
      BILLINGDOCUMENT       = v_invoic
TESTRUN               =
NO_COMMIT             =
BILLINGDATE           =
    TABLES
      RETURN                = i_cret
      SUCCESS               = i_csucess
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
       EXPORTING
            WAIT   = space
       IMPORTING
            RETURN = i_ret2.
read table i_cret with key type = 'E'.
if sy-subrc ne 0.
    message i005 with v_invoic.
    stop.
endif.
ENDFORM.                    " cancel_invoice
*&      Form reverse_goodsissue
      Reverse the goods Issue
FORM reverse_goodsissue.
Local Variable
data : lv_vbtyp like likp-vbtyp.
clear : i_mesg,
          lv_vbtyp.
refresh : i_mesg.
select single vbtyp from likp into lv_vbtyp
                           where vbeln = v_deliv.
CALL FUNCTION 'WS_REVERSE_GOODS_ISSUE'
    EXPORTING
      I_VBELN                         = v_deliv
      I_BUDAT                         = sy-datum
    I_COUNT                         =
    I_MBLNR                         =
    I_TCODE                         =
      I_VBTYP                         = lv_vbtyp
    TABLES
      T_MESG                          = i_mesg
   EXCEPTIONS
     ERROR_REVERSE_GOODS_ISSUE       = 1
     OTHERS                          = 2
if sy-subrc ne 0.
    message i007 with v_deliv.
endif.
ENDFORM.                    " reverse_goodsissue
*&      Form get_sales_deliv
      Get the Sales order and Deliv Items
FORM get_sales_deliv.
Local Variables
data : lv_kwmeng like vbap-kwmeng.
clear : i_lips,
          i_vbap.
refresh : i_lips,
            i_vbap.
Select the data from LIPS
select * from lips into table i_lips
                     where vbeln = v_deliv.
if sy-subrc ne 0.
    message i008 with v_deliv.
    stop.
endif.
sort i_lips by vbeln posnr.
Get the Sales order Item Data.
select * from vbap into table i_vbap
                          where vbeln = p_vbeln.
if sy-subrc ne 0.
    message i006 with p_vbeln.
    stop.
endif.
sort i_vbap by vbeln posnr.
Compare delivery Item and Order Items
loop at i_lips.
    clear lv_kwmeng.
    read table i_vbap with key posnr = i_lips-posnr.
    if sy-subrc eq 0.
      lv_kwmeng = i_vbap-kwmeng * 2.
      if lv_kwmeng >= i_lips-lfimg.
        i_lips-lfimg = i_vbap-kwmeng.
        modify i_lips.
      endif.
    endif.
endloop.
ENDFORM.                    " get_sales_deliv
*&      Form Delivery_change
      Delivery Update
FORM Delivery_change.
Clear : i_prot.
refresh : i_prot.
Delivery Update
CALL FUNCTION 'LE_MOB_DELIVERY_UPDATE'
       EXPORTING
            do_commit                = 'X'
       TABLES
            t_delivery_items         = i_lips
            prot                     = i_prot
       EXCEPTIONS
            conversion_overflow      = 1
            essential_data_missing   = 2
            error                    = 3
            nothing_to_update        = 4
            lock_after_update_failed = 5
            error_in_delivery_update = 6
            OTHERS                   = 7.
COMMIT WORK.
IF sy-subrc <> 0.
    MESSAGE i009 with v_deliv.
endif.
Post Goods Issue
CLEAR:    d_return,
            i_prot,
            l_vbeln,
            l_vbkok.
REFRESH i_prot.
CLEAR: ef_error_in_item_deletion_0    ,
          ef_error_in_pod_update_0       ,
          ef_error_in_interface_0        ,
          ef_error_in_goods_issue_0      ,
          ef_error_in_final_check_0      .
carry out goods issue
l_vbeln          = v_deliv.
l_vbkok-vbeln_vl = l_vbeln.
l_vbkok-wabuc    = 'X'.
carry out goods issue
l_vbeln          = v_deliv.
l_vbkok-vbeln_vl = l_vbeln.
l_vbkok-wabuc    = 'X'.
SET UPDATE TASK LOCAL.
CALL FUNCTION 'WS_DELIVERY_UPDATE'
       EXPORTING
            vbkok_wa                    = l_vbkok
            synchron                    = 'X'
            no_messages_update          = ' '
            update_picking              = 'X'
            commit                      = 'X'
            delivery                    = l_vbeln
            nicht_sperren               = 'X'
            if_error_messages_send_0    = space
       IMPORTING
            ef_error_any_0              = ef_error_any_0
            ef_error_in_item_deletion_0 = ef_error_in_item_deletion_0
            ef_error_in_pod_update_0    = ef_error_in_pod_update_0
            ef_error_in_interface_0     = ef_error_in_interface_0
            ef_error_in_goods_issue_0   = ef_error_in_goods_issue_0
            ef_error_in_final_check_0   = ef_error_in_final_check_0
       TABLES
            prot                        = i_prot
       EXCEPTIONS
            error_message               = 1
            OTHERS                      = 2.
if sy-subrc ne 0.
    message i010 with v_deliv.
else.
    COMMIT WORK .
endif.
ENDFORM.                    " Delivery_change
*&      Form invoice_create
      Invoice Creation
FORM invoice_create.
refresh: XKOMFK, XKOMV,
           XTHEAD, XVBFS,
           XVBPA, XVBRK,
           XVBRP, XVBSS.
clear : XKOMFK, XKOMV,
           XTHEAD, XVBFS,
           XVBPA, XVBRK,
           XVBRP, XVBSS,
           VBSK_I.
VBSK_I-SMART = 'F'.
XKOMFK-VBELN = v_deliv.
XKOMFK-VBTYP = 'J'.
APPEND XKOMFK.
CALL FUNCTION 'RV_INVOICE_CREATE'
       EXPORTING
            VBSK_I       = VBSK_I
            WITH_POSTING = 'C'
       TABLES
            XKOMFK       = XKOMFK
            XKOMV        = XKOMV
            XTHEAD       = XTHEAD
            XVBFS        = XVBFS
            XVBPA        = XVBPA
            XVBRK        = XVBRK
            XVBRP        = XVBRP
            XVBSS        = XVBSS.
if sy-subrc eq 0.
    COMMIT WORK.
   flag = 'X'.
else.
message i011 with p_vbeln.
endif.
ENDFORM.                    " invoice_create
Thanks
Seshu

Mass processing for forecating in SOP

Hi all
I ma able to forecast a material online thru MC87 in standard SOP, but when I try to set up a variant for mass processing in the background the forecasting does not work. Has anybody encountered this issue?
thanks a lot

Tajuddin
Thanks for your reply. I am reading the R/3 documentation and it talks about Mass processing of SOP forecasting ( R/3 documentation verbiage below) I am trying to follow these steps but it does not work. Isn't this mass processing supposed to be for forecasting in mass in background?
Am i understanding this incorrectly?
How to Run the Forecast with Mass Processing
You can use SOPs mass processing function to run the forecast. In this process:
You create a forecast profile.
You create a planning activity and include in it this action (the forecast profile).
You create a mass processing job for this activity.
You schedule this mass processing job.
The results of the forecast will be different if the forecast is run at a high level and the results then disaggregated to the detailed level than if you carry out the forecast at the detailed level.

Mass Variant for OBD creation+PGI

Similar Messages

Maybe you are looking for