Mapping Document date to PO date during MASS Transaction

Hi ABAP Experts,
I have a quick question. I want to change existing Sales order header data. I think we can do it using MASS transaction.
Right now we don't have any data in the PO date field. Now I want to fill this field using document date.
I went to MASS transaction and there is feature to set a rule to get this value. Someone please give me the code to get document date and put it in the X value.
Here is the existing form routine the system gave.
* X is the value you must return
form GET_NEW_MASSSDHEAD_S_BSTDK
using segment structure MASSSDHEAD_S
changing X.
endform
Thanks and awaiting your answer,
Creasy Matt
Edited by: Creasy Matthew on Nov 10, 2008 8:08 PM

please check this
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CAGTFMS/CAGTFMS.pdf

Similar Messages

  • Data Mapping Document

    Hi,
    I am part of a Data Migration project involves source system (SAP). And target Systems (peopleSoft And JDEdwards). now we want to do Data Mapping for these Source And Target Systems. Any Body Provide me with some Data Mapping Documents How to map the Fields Between these systems. Thanks in advance.
    Thanks
    kiran.B

    Hi Kiran,
    We are also converting from Peoplesoft to SAP, for HR. Can you please share your mapping document, if any, to following email address.
    shettyvk(at the rate)gmail(dot)com
    Thanks...
    Vinay

  • Is there any Data Mapping document Between S&OP ( model that uses supply planning operator ) and SAP ECC that I will help the client in Data Mapping activity.

    Hello All,
    Is there any Data Mapping document Between S&OP ( model that uses supply planning operator ) and SAP ECC that I will help in Data Mapping activity.
    Thanks,
    Mownesh

    There are standard templates in HCI data sources.
    e.g. 1) Customer Master data template is SOP_MD_CustomerMaster for extracting master data from SAP ECC and load it to S&OP
    KNVP is the table for customer in ECC from that you can select the fields as required
    KUNNR for customer Number
    ADRNR for Address
    List of a few commonly used table names of ECC:
    Product Related:
    MARA – Material Master (MATNR)
    MARC – Material Master with Plant Data (MATNR, WERKS)
    MARD – Material Master with Storage Location Data (MATNR, LGORT, WERKS)
    MAKT – Material Master Material Descriptions (MATNR, MATKL)
    MBEW – Material Valuation Data (MATNR, BWTAR)
    MVKE – Material Master : Sales related Data
    MDKP, MDTB – MRP related Data( Header, Item)
    MCHA, MCHB – Material Batches (Header, Item) (MATNR, WERKS, LGORT, CHARG)
    Vendor/Supplier related:
    LFA1 – vendor data (LIFNR)
    LFB1 --  Company Code Segment : Vendor Data(LIFNR, BUKRS)
    LFC1 --  FI Related Vendor Data (LIFNR, BELNR)
    LFM1 – Pur. Orgn. Related Vendor Data (LIFNR, EKORG)
    PReq/PO, BOM Related:
    EBAN – Pur. Req. Data( BANFN, BNFPO, BADAT, MATNR)
    EINA – Purchase Info. Record(General Data)(INFNR, MATNR, LIFNR)
    EINE – Purchase Info. Record (pur. Orgn. Data) (INFNR, EKORG)
    ELBK, ELBN, ELBP – Vendor Evaluation Related Data
    EKKO – PO Data (Header) (EBELN, BSTYP, BSART)
    EKPO – PO Data (Item) (EBELN, EBELP, MATNR)
    Pur. Req., RFQ and PO are differentiated by Doc Type (BSTYP) in EKKO table.
    For RFQ it is ‘A’ and for PO it is ‘F’
    MKPF – GRN Data (Header) (EBELN, BLDAT, BUDAT, XBLNR, BKTXT)
    MSEG – GRN Data(Item) MBLNR, BWART, LIFNR, MATNR, EBELN)
    Apart from this there are lot of tables which begin with ‘M’ & ‘E’, but we
    use the following very often.
    EQUK – Quota (Header)(QUNUM, MATNR)
    EQUP – Quota (Item) (QUNUM, QUPOS, LIFNR)
    EKBE – PO History Data (EBELN, EBELP, BELNR, BLDAT, MATNR, VGABE)
    EKBZ – PO History with Delivery Costs(EBELN, BELNR, LIFNR, XBLNR)
    EKET – Schedule lines data of a PO(EBELN, EINDT, SLFDT)
    EKES – Vendor Confirmations Data (EBELN, EBTYP, EINDT, XBLNR)
    T163F – Confirmation Texts (EBTYP, EBTXT)
    T156 – Movement Types (BWARE)
    T024 – Purchasing Groups
    T024E – Purchase Organizations
    T163 – Item Category’s in Purchasing Documents(PSTYP)
    T149D – Valuation Types
    T134 – Material Types
    FVLK – Delivery Types
    STKO, STPO – BOM(Bill Of Material) related Data (Header & Item)
    STPU, STPN, STST, STZU – BOM Related Tables
    RKPF, RBKP, RSEG (Header & Item) – MM – FI Related Data
    KONO, KONH – Pricing data
    T006 – Basic Unit Of Measurements
    Customer/Sales Order Related:
    VBAK : Sales Document(Header Data) (VBELN)
    VBAP : Sales Document(Item Data) (VBELN, POSNR, MATNR, ARKTX, CHARG)
    Enquiry, Quotation, Sales Order are differentiated based on Doc.
    Type(VBTYP Field) in VBAK, VBAP Tables for Enquiry VBTYP = A, for Quotation ‘B’ & for Order it is ‘C’.)
    LIKP : Delivery Table(Header Data) (VBELN, LFART, KUNNR, WADAT, INCOL)
    LIPS : Delivery Table(Item Data)(VBELN, POSNR, WERKS, LGORT, MATNR, VGBEL)
    (LIPS – VBGELN = VBAK- VBELN, LIPS-VGPOS = VBAP-POSNR)
    VTTK : Shipment Table(Header Data) (TKNUM)
    VTTP : Shipment Table (Item Data)(TKNUM, TPNUM, VBELN)
    (VTTP – VBELN = LIKP – VBELN)
    VBRK : Billing Table(Header Data) (VBELN, FKART, BELNF)
    VBRP : Billing Table(Item Data) (VBELN, POSNR, FKIMG, NEWR, VGBEL, VGPOS)
    (VERP – AUBEL = VBAK- VBELN, VBRP – VBEL = LIKP – VBELN)
    Apart from these tables there are lot of other tables which starts with ‘V’, but we use the
    following tables frequently.
    VBUK: All Sales Documents status & Admn. Data(Header) (VBELN, VBTYP)
    VBTYP = ‘C’ (Sales Order) VBTYP = ‘L’(Delivery) VBTYP = ‘M’(Invoice)
    VBUP: Sales Documents status & Admin. Data(Item) (VBELN, POSNR)
    VBEP : Sales Document Schedule Lines Data (VBELN, POSNR, EDATU, WMENG)
    VBKD: To get sales related Business data like Payment terms etc.(VBELN, ZTERM)
    VBFA: Sales Document flow data(VBELV, VBELN, POSNV, VBTYP)
    VBPA: Partner functions Data(VBELN, PARVW, KUNNR, LIFNR)
    TVLKT: Delivery Type: Texts(LFART, VTEXT)
    KNA1, KNB1, KNC1 : Customer Master Data and Other Partner’s Data(KUNNR,
    NAME1,LAND1)
    KNVK: Customer Master Contact Person(PARNR, KUNNR)
    KNVV: Customer Master Sales Data.
    LFA1, LFB1, LFC1: Vendor Master Data(To get Transporter data)(LIFNR, NAME1, ORT01)
    MARA, MARC, MARD : Material Master Data(Basic, Plant, St. Location Views)
    TVKO: Sales Organizations(VKORG)
    TVKOV: Distribution Channels(VTWEG)
    TVTA: Divisions(SPART)
    TVKBZ: Sales Office(VKBUR)
    TVBVK: Sales Group(VKGRP)
    T077D: Customer Account Group(KTOKD)
    T001W: Plants(WERKS)
    T001L: Storage Locations(LGORT)
    TWLAD: To get address of Storage Location and Plant(LGORT, ADRNR)
    TVAU: Sales Document (Order) Types
    KONV: Condition Types (pricing) (KNUMV, KSCHL, KWETR)
    T685T: Condition Types Texts.
    ADRC: To get Addresses of Partners
    VBBE, VBBS: Sales Requirements Data
    VBKA: Sales Activities Data
    VBPV: Sales Document Product Proposal
    Based on the functionality you can search ECC table names and fields
    Hope this information is helpful for you.
    Thanks and Regards,
    Anjali

  • Mass change of pricing date and billing date in credit memo request

    Hi,
    Can i change the billing date pricing date on credit memo request docs using MASS transaction?
    If i enter the regular sales order number it prompts me to change the value but if i enter the credit memo request doc number,the message "No data meets the selection criteria" is displayed.I also checked with IDES ,message is the same
    Is there any different way to do mass change for credit memo requests or am i missing something here.
    Please Suggest
    Thanks
    Abhilash Nayak

    Hi,
    Go to the transaction code MASS  and enter the OBJECT  TYPE as BUS2032 and enter
    It will lead you to the next screen where you can find the  Table and Field TABS
    Select the  SALES ORDER HEADER DATA  and choose the fields data and choose the fields PRICING DATE and BILLING DATE  and execute
    In the subsequent screen you can see the selection screen where you can enter all the Sales documents for which you want to change
    Key in all the documents and execute
    Now change the date as per your requirement and check the effect
    regards,
    santosh

  • Disk Utility - Partition map needs repair because a data partition needs loader space.

    I just finished setting up both my OSX and Windows installs from scratch after fitting an SSD, which in-turn was right before my logic board died and Apple replaced it, now it looks like I have some sort of hard drive issue brewing.
    This was my plan for the SSD, and how it currently displays in Disk Utility although that wasn't the case earlier:
    And in Terminal:
    My intention was to have two boot partitions for each OS, 'Macintosh HD' and 'Win 7 Pro' and a third shared data partition 'Projects' on the SSD, which I made in Drive Genius after installing Boot Camp. I don't want Macintosh HD accessible from Windows because I'll be using Paragon HFS+ or MacDrive to give write access and don't want OSs stomping on other OSs turf, hence needing three partitions. Everything looked fine until I just checked Disk Management under windows and realised it couldn't see the Projects volume. Even though it's fine in OS X, it was just marked black/unallocated space.
    So I booted back into OSX, all my files look fine so I ran Disk Utility and the Partition tab looked really odd - unfortunately I didn't get a screenshot. All volumes reported their size correctly but visually, Macintosh HD took up most of the drive. I could see 'Windows 7 Pro' under this, but the Partition Layout section had a scrollbar, which if I scrolled down showed 'Projects' squished into a tiny gap at the bottom. I ran a Verify, which reported no problems, and at some time since the Partition Layout has reverted to how it should look (as in the screenshot above), with 'Projects' book-ended by "Macintosh HD' and 'Windows 7 Pro'.
    Now when I run a Verify on Macintosh HD or Projects volumes, it says there's no problem, but if I run one on the drive, I get this message:
    Volume Macintosh HD on disk0s2 has 0 bytes of trailing loader space and it needs 134217728 bytes
    Problems were found with the partition map which might prevent booting
    Error: Partition map needs repair because a data partition needs loader space.
    I've only managed to find one other mention of this error here, but the fix is not relevant to me because I don't have Sophos installed. I've tried Single User/Safe Mode but it just boots into normal mode, so I can't do a fsck -fy.
    ** /dev/rdisk0s2 (NO WRITE)
    Can't open /dev/rdisk0s2: Permission denied
    That value in bytes is exactly 128mb, so I suspect the problem lies with one of the invisible partitions that show up in iPartition and Disk Management under Windows, but not in Disk Utility. I have backups and I suspect the root of the problem is partitioning in iPartition after installing Boot Camp, but I've never had issues with this approach in the past so I'm wary of just giving up and reinstalling Windows again will be massive hassle because I no longer have a SuperDrive and last time it refused to install from USB.
    Anyone have any idea what's going on? It seems like the sort of issue Disk Utility should just handle, at least in Recovery mode, but it's not playing ball. It also doesn't seem like a massive problem since my files all look fine and performance is OK, so I'm reluctant to do anything major.
    I'll update with a shot of the drive in Disk Management from Windows in a few minutes, in case that sheds light on anything. Thanks!

    Similar issue here. I manually partitioned my hard disk for triple boot (using Gparted on Linux), then everything was just fine until I ran bootcamp, to do something as simple as create a boot USB.
    I get the same error as a result and have to work my way into booting, by resorting first to a Linux live USB, then restarting from the live USB, to finally reach my rEFInd boot manager, or whichever boot manager should be initialized at startup.
    I suppose that the cause in my case is that some operation "scratched" the protective MBR. See this:
    http://www.mactech.com/articles/mactech/Vol.23/23.03/APMtoGPT/index.html
    I am hoping to fix it using an external Yosemite installation media: see this guide -
    http://www.macworld.com/article/2367748/how-to-make-a-bootable-os-x-10-10-yosemi te-install-drive.html
    And as a last resort to reinstall.
    I'll admit I am negatively surprised. I need this computer for professional reasons, and for the sake of "preserving the integrity of OSX", measures defined by Apple instead tend to make partitions far easier to damage. And this problem seems to affect a number of users.
    As for what I have to go through to fix it: a 5GB download, during which I have to register my credit card to the Apple Store. "Pay first, get your free software next."
    IF Disk Utility can fix it, from the external media, then fair enough. The hassle is unpleasant but it files as "a choice".
    Otherwise you can file it safely under software design calamity.

  • Posting Document not created (export data missing)

    We are working on ECC 6.0 and during creation of Cancellation Billing document type IVS for the Intercompany billing, the document did not create Accounting document giving the Posting status as G - Posting document not created (export data missing). However checked the Foreign trade data and the system states that Foreign trade is complete.
    Can any one suggest the solution for this?
    Thanks.

    Hello Mohammad,
    About this issue, the incompletion of this cancellation document
    arises might because the reference delivery has been archived/deleted.
    This is likely due to your current copy control settings (VTFL).
    If you have set ' ', in the export determination field this means that
    there is a common 'exnum' key between the delivery and billing documents
    LIKP-EXNUM & VBRK-EXNUM are the same.
    The result of deleting the delivery is that you also delete the FT data
    for the delivery, Because the billing document and delivery share the
    same foreign trade table entries, you have in effect deleted the FT data
    of the billing document too. This would most likely go unnoticed but if
    you then cancel the invoice the system has no FT to copy into the new
    cancellation billing document, which leads to this issue.
    Firstly you should set the export determination flag in the copy control
    of the delivery & billing documents. This will avoid this issue in the
    future. Set it to to 'A' or 'B' depending on your requirements.
    For the incomplete cancellation billing document, you could use userexit to
    set it as complete:
    You can use transaction CMOD.
    Create a project for example FT project button create short text: ....
    drop button Enhancement assignment & save use for example local object.
    Use the F4-help for Enhancement and look for V50EPROP.
    Drop button Components:
    here you will find EXIT_SAPLV50E_005 and EXIT_SAPLV50E_006
    In the userexits doubleclick on the includes ZXV50U05 and ZXV50U06
    The coding in the userexits should be: C_COMPLETE = 'X'.
    Afterwards activate generate ... and save.
    The development class is VEI.
    Please also check note 118573 which explains the FT user exits.
    Regards,
    Alex

  • How to coorect a reversed document but wrong valuation date

    Hello Experts,
    We are on our closing activity right now.
    But we have encountered a problem wherein we reversed a billing with corresponding issuance (601).The original posting has a valution date (sample: 7/23/2009) of the period we are closing, but the reversal has a valuation of the next period (Aug 3, 2009). Now the account connected to the reversal has gathererd the MAP for the next period (Aug 3, 2009).
    So right now we are having a discrepancy on the Account connected to the transaction since different MAP are gathered since valuation date of the two transactions are not on the same period.
    How can I solved this......?
    Thanks Gurus.

    As you may be aware for any SD document, if corresponding Accounting Document is generated, then you cannot make any adjustments from SD side.  It has to be addressed from FI side only where they have to pass JV
    thanks
    G. Lakshmipathi

  • Cannot reverse document with future posting date

    Hi,
    When I tried to reverse a document with future posting date, system gives error F5362 Posting date must not be smaller than XX.XX.XXXX (x = future posting date).
    Is it possible to do this in SAP?

    Hello,
    You need to use reversal reason configured accordingly.
    Configure the reversal reason for your purpose:
    IMG => Financial Accounting => Business Transactions => Adjustment Posting / Reversal / Define Reasons for Reversal
    Make SURE that you have ticked Alt.Pos.dt (Alternative Posting Date) check box.
    Save it.
    Now use this reversal reason for your posting and give a fugure date.
    Make sure that the future posting period is opened but NOT closed.
    Please also read F1 on alternative posting date check box:
    Indicator: Alternative posting date allowed
    Indicator as to whether you are allowed to specify an alternative posting date for the relevant reversal reason.
    Use
    When you use the reversal reason, the system checks that reversal is not carried out using an alternative posting date and therefore possibly in a later posting period or in a later fiscal year.
    Examples
    If you want to use negative postings during reversal but only if the reversal is posted in the same period, you can define two reversal reasons:
    1st reason: No alternative date allowed, generate negative posting
    2nd reason: Alternative date allowed, do not generate negative posting
    Regards,
    Ravi

  • Mapping webservice result to a Data Type

    Hi,
    I receive an array of String objects as a result of a webservice call. These String Objects are XML documents (but as String Object...). How can I take each element of the array and extract all tags values to be mapped to a pre-defined Data Type? Have I to implement a parser in an UDF? How can I do the same mapping for each array cell automatically?
    Thanks!

    Use a simple XSLT to extract the xml document from a particular string.
    Suppose the response XML is like:
    <OutputMessage>
    <string></string>
    </OutputMessage>
    Your xslt would be something like:
    <xsl:template match="/OutputMessage/string">
    <xsl:value-of select="." disable-output-escaping="yes"/>
    </xsl:template>
    If you have more than 1 string, create a root tag and extract all of them inside that tag.
    Regards,
    Henrique.

  • Want Document date in Translation date when we are doing MIGO.

    Hi Expert,
    While doing MIGO, my client needs "Document date" in "Translation date " when we click "FI Document" button.
    Even i tried badi "FI_TRANS_DATE_DERIVE". but this is working fine for maximum transaction but not working for MIGO.
    Could any body help me on this....
    Regards
    Sanjay Kr.

    Hi Amaresh,
    Without mapping its difficult to achieve, you have to create custom adapter module or you could try below steps.
    1. Configure your receiver file adapter to create files with same source file name
    2. Write script to rename the file based on your requirement.
    3. Call the script in Run OS command after message processing in receiver file adapter.
    Regards,
    Praveen

  • OVI Maps keeps wanting to download data after upda...

    I have the Nokia 5230 which I bought in July. I had also installed the OVI suite on my PC, which I used to download the full map of Malaysia and Singapore. I could happily use the GPS function without having to download large amount of data through the phone, or allow it to go online if I want to search for location. In the case where I wanted to use it offline, zooming in or out at any level allows me to see the roads and place names clearly.
    A few days back while using OVI Maps, a popup came up saying a new version is available. I promptly allowed the download, but installation failed saying there "was not enough memory".
    I uninstalled apps from my phone, including "Nokia Maps". After clearing up apps and getting about  40MB free memory, was I able to install the new version of OVI maps. I promptly re-downloaded the Malaysian and Singapore Maps through Ovi SUite.
    Now I notice OVI Maps now download large chunks of data through my data connection during GPS usage. If I disallow online use, my GPS shows  nothing but a blank "map". If I allow going online for the first time, and not the second time, when using GPS, the same blank appears if I zoom out or zoom in. It's as if the maps are not there, so data connection is required to download them. How can this be when I have already downloaded the Malaysian / Singaporean map to my phone through OVI suite? I have set on my phone and the OVI suite for the data to be saved to my microSD card.
    Please help. This is driving me up the wall.

    Here's what you can try to do.
    1. Back up your phone memory.
    2. Update the phone software.
    3. Download Ovi Maps in this link : http://maps.nokia.com/services-and-apps/ovi-maps/free-downloads#/nokia-5230/
    4. Remove the "qf" and "Cities" folder on your memory card.
    5. Install the Maps Application on the newly updated phone.
    6. Once the installation is successful, run the Maps on your phone but don't go online. This will re create the two folders that you deleted in the memory card.
    7. Open Settings of the maps application then click on maps. Make sure that it will use the maximum allowable size (90%)
    8. Download the Maps data again using Ovi Suite.
    Every one can correct if I'm wrong. ^_^

  • Regarding : Material document data and PO data do not match (Plant)

    Hi Gurus,
    Please go through this BAPI program.
    While uploading it is giving an error ' Material document data and PO data do not match (Plant) '.
    Please help regarding this issue.For all Other moment types it is working fine except this 351 moment type.
    dATA: i_excel TYPE truxs_t_text_data. "work table for excel upload
    DATA: BEGIN OF it_itab OCCURS 100,
          docdate(10),
          postdate(10),
          mvt_type(3), "Movement Type
          plant(4), "Plant
          lgort(4),
          pur_doc(10), "Purchase Document No
          po_item(3), "Purchase Document Item No
          material(18), "Material Number
         delnote(16),
          erfmg(13),
          uom(3),
         lfmng(13), "Quantity
          batch(10) TYPE c,
          vfdat TYPE vfdat,
          END OF it_itab.
    DATA: it_goodsmvt_head TYPE TABLE OF bapi2017_gm_head_01      INITIAL SIZE 100,
          it_goodsmvt_code TYPE TABLE OF bapi2017_gm_code         INITIAL SIZE 100,
          it_goodsmvt_item TYPE TABLE OF bapi2017_gm_item_create  INITIAL SIZE 100.
    DATA: wa_goodsmvt_head LIKE LINE OF it_goodsmvt_head,
          wa_goodsmvt_code LIKE LINE OF it_goodsmvt_code,
          wa_goodsmvt_item LIKE LINE OF it_goodsmvt_item.
    DATA: w_mat_doc  TYPE bapi2017_gm_head_ret-mat_doc,
          w_year     TYPE bapi2017_gm_head_ret-doc_year.
    DATA: BEGIN OF it_errmsg_goodsmvt OCCURS 10.
            INCLUDE STRUCTURE bapiret2.
    DATA: END OF it_errmsg_goodsmvt.
    DATA : obj_type LIKE bapiache09-obj_type,
           obj_key  LIKE bapiache09-obj_key,
           obj_sys  LIKE bapiache09-obj_sys.
    DATA: v_date1 TYPE sy-datum.
    DATA: v_date2 TYPE sy-datum.
    DATA: w_lines TYPE i.
    DATA: errflag.
    SELECTION-SCREEN BEGIN OF BLOCK bk1 WITH FRAME TITLE text-100.
    PARAMETERS: p_file TYPE  rlgrap-filename.
    SELECTION-SCREEN END OF BLOCK bk1.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
      CALL FUNCTION 'F4_FILENAME'
        EXPORTING
          field_name = 'P_FILE'
        IMPORTING
          file_name  = p_file.
    Start-of-selection processing
    START-OF-SELECTION.
      CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
        EXPORTING
          i_line_header        = 'X'
          i_tab_raw_data       = i_excel
          i_filename           = p_file
        TABLES
          i_tab_converted_data = it_itab[]
        EXCEPTIONS
          conversion_failed    = 1
          OTHERS               = 2.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ENDIF.
      LOOP AT it_itab.
        REFRESH it_goodsmvt_head.
        REFRESH it_goodsmvt_item.
        CONCATENATE it_itab-docdate6(4) it_itab-docdate3(2) it_itab-docdate+0(2) INTO v_date1.
        CONCATENATE it_itab-postdate6(4) it_itab-postdate3(2) it_itab-postdate+0(2) INTO v_date2.
        wa_goodsmvt_head-pstng_date = v_date2.
        wa_goodsmvt_head-doc_date   = v_date1.
       wa_goodsmvt_head-ref_doc_no = it_itab-delnote.
    wa_goodsmvt_head-pr_uname   = sy-uname.
        APPEND wa_goodsmvt_head TO it_goodsmvt_head.
    Maintain it_goodsmvt_code
        wa_goodsmvt_code-gm_code    = '04'.
    Maintain it_goodsmvt_item
    *LOOP AT it_itab.
    IF wa_goodsmvt_item-po_number IS INITIAL.
        wa_goodsmvt_item-po_number    = it_itab-pur_doc.
        wa_goodsmvt_item-move_type    = it_itab-mvt_type.
        wa_goodsmvt_item-MOVE_PLANT      = it_itab-plant.
        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
          EXPORTING
            input  = it_itab-material
          IMPORTING
            output = it_itab-material.
        wa_goodsmvt_item-material     = it_itab-material.
        wa_goodsmvt_item-stge_loc     = it_itab-lgort.
        wa_goodsmvt_item-po_item      = it_itab-po_item.
        wa_goodsmvt_item-entry_qnt    = it_itab-erfmg.
        wa_goodsmvt_item-ENTRY_UOM_ISO    = it_itab-uom.
       wa_goodsmvt_item-po_pr_qnt    = it_itab-lfmng.
        wa_goodsmvt_item-batch        = it_itab-batch.
        wa_goodsmvt_item-expirydate   = it_itab-vfdat.
       wa_goodsmvt_item-NO_MORE_GR   = 'X'.
        wa_goodsmvt_item-mvt_ind      = 'B'.
        APPEND wa_goodsmvt_item TO it_goodsmvt_item.
        CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
          EXPORTING
            goodsmvt_header  = wa_goodsmvt_head
            goodsmvt_code    = wa_goodsmvt_code
          IMPORTING
            materialdocument = w_mat_doc
          TABLES
            goodsmvt_item    = it_goodsmvt_item
            return           = it_errmsg_goodsmvt.
    Process of commit work
        IF it_goodsmvt_head[] IS NOT INITIAL.
          DESCRIBE TABLE it_goodsmvt_head LINES w_lines.
        ENDIF.
        IF it_goodsmvt_item[] IS NOT INITIAL.
          DESCRIBE TABLE it_goodsmvt_item LINES w_lines.
          CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
            EXPORTING
              wait = 'X'.
        IMPORTING
        RETURN        =
          CLEAR errflag.
          READ TABLE it_errmsg_goodsmvt INDEX 1.
          IF it_errmsg_goodsmvt-type EQ 'E'.
            WRITE:/'Error in function', it_errmsg_goodsmvt-message.
            errflag = 'X'.
          ELSE.
            WRITE:/ it_errmsg_goodsmvt-message.
          ENDIF.
          IF errflag IS INITIAL.
            COMMIT WORK AND WAIT.
            IF sy-subrc NE 0.
              WRITE:/ 'Error in updating'.
              EXIT.
            ELSE.
              WRITE:/ 'Material Document created successfully and the Document Number for the Material',
                      wa_goodsmvt_item-material,'is:', w_mat_doc, w_year.
            ENDIF.
          ENDIF.
        ENDIF.
      ENDLOOP.

    Hey,
    Just wanted to post that in my case this was the error of MVT_IND field in item table. When I made it from 'B' to blank then it worked.
    Mine is solved....
    Thanks

  • Not to allow to save the billing document in the back date if FI period clo

    Can anybody help me please. My FI period for october is closed. But there are still some open delivery documents in billing due list for October. So now let say on 7th december if i will make the billing documents by giving the date 30.11.2007 logically as FI period is closed it will allow to save the billing document but will not pass to accounting.
    So this normaly happening in my industry endusers are creating the billing documents in the back date even after the period close so all the documents come into VFX3.
    So can any body help me? Can we have any check if the FI period is closed for a perticular months if we will try to make the billing documents in the closed period it will not allow to generate the billing document rather saving the documents and blocking for accounting.
    Reggards.
    Laxmikanta Das.
    09958119889.

    Dear laxmikanta
    I also not come across the situation what you said and hence dont have much idea about authorization group.
    However, on going through the F1 help, it says
    <b>Procedure</b>
        If only a limited set of users is to be able to post in a particular
        posting period, proceed as follows:
                 o   Add the posting period authorization (authorization object
            F_BKPF_BUP) to the authorizations of the selected users. Assign an
            authorization group (e.g. '0001').
                  o   Enter the account type '+' for the posting period variant to which
            the restriction is to apply. Enter the period(s) whose use is to be
            restricted in the first period, those which are available to all
            users in the second period, and the authorization group (e.g.
            '0001') in the last column.
    <b>Examples</b>
        A posting period can be successively restricted. If, e.g. 10 users have
        the posting period authorization with authorization group '0001', and 3
        of these 10 users also with authorization group '0002'.
        If the period is only to be accessible to the 10 selected users the
        authorization group '0001' is entered in the posting period variant.
        Access can later be restricted to the remaining 3 users by entering
        '0002'.
    From the above, I feel your requirement can be met.
    Thanks
    G. Lakshmipathi

  • Error in mapping generation when using a data rule

    I hope someone can point me in the right direction on this one. I've searched all over but can't find a similar problem anywhere.
    This is OWB Client 10.2.0.1.31 and repository 10.2.0.1.0 in a 10g SE database . I have a table on which I have defined a data rule, which is deployed in the database along with its corresponding error table. The rule I have used is the built-in IS_DATE and it is applied to a VARCHAR2 field that will store a date in a specific format. I have defined the table as an operator in a mapping, and set the IS_DATE data rule action to MOVE TO ERROR. When I try to deploy the mapping I get the follwoing errors in the log:
    Warning ORA-06550: line 244, column 4:
    PL/SQL: ORA-00907: missing right parenthesis
    Warning ORA-06550: line 221, column 3:
    PL/SQL: SQL Statement ignored
    Warning ORA-06550: line 3112, column 132:
    PLS-00103: Encountered the symbol "DD" when expecting one of the following:
    . ( ) , * @ % & | = - + < / > at in is mod remainder not
    range rem => .. <an exponent (**)> <> or != or ~= >= <= <>
    and or like LIKE2_ LIKE4_ LIKEC_ between || multiset member
    SUBMULTISET_
    The symbol "." was substituted for "DD" to continue.
    When I look at the generated code, there are lines like this one:
    not (wb_to_date("table"."column", Month dd, RRRR, Mon dd, RRRR, MM-DD-RRRR, MM/DD/RRRR, YYYY-MM-DD, YYYY/MM/DD) is not null
    Why is OWB not putting single quotes around the data formats from the built-in data rule? Is there something fundamental I'm missing in my warehouse model?

    Hi
    This is bug 5195315, which looks to be fixed in a 10.2 patch. If you can pick up the latest 10.2 patch there is like 3 years of fixes worth picking up.
    Cheers
    David

  • Status 51 material document data and po data do not match(vendor)

    i am using we19 to try an inbound idoc mbgmcr(receipt for po)
    i put in gm_code 01
    movement indicator B(goods receipt for po)
    vendor 3815
    PO 4500015241
    PO Order Item 00030
    Movement type 101
    qty in unit of entry  1
    iso code unit of measurement pc
    on the po screen i see the po item and qty to be delivered is 75
    when i run the inbound idoc i get
    status 51 material document data and po data do not match(vendor) but as i say on the po inquiry screen i see the po vendor item with 75 to be delivered
    what am i missing????????????????

    thank you
    i put in the leading zeros and got rid of that problem
    now i am getting status 51
    posting only possible in 2004/07 and 2004/06
    but in the posting date i use 07/02/2004  i have tried several dates in the period but get the same error
    any ideas?
    thanks you

Maybe you are looking for