Trigger CIF during custom field change on Purchase Req. and PO

Hi,
We added a custom date field in Purchase Req. and Purchase Order transactions (ME52N/ME22N) in ECC. When this custom field gets changed along with any other standard field, outbound CIF process happens. However, when we change this custom field only, then outbound CIF doesn't happen. I believe we need change pointers and may be custom code to trigger outbound CIF. I would appreciate any suggestions on how to achieve this functionality.
Thanks.
Naveen

Hello Naveen,
Use user exit EXIT_SAPLMEAP_001 here, the structure CIFPUORCUS must be enhanced with custom fields so that the document date can be included (IT_OUTPUT_CUS).transferred to CT_MM_DOC. You need to fill EBAN and EKPO for change transfer. Also you can have the background job for RIMODINI to transfer the changes.
Best Regards,
R.Brahmankar

Similar Messages

  • Adding up a Custom Field Approver in Purchase Requisition

    Hi,
      Could anyone please let me know how to addup a custom field Approver to Purchase Requistion.
       Requesting you to list down the User enhancements that are available for PR Lineitems screen.
       The transaction used is ME51N.
    Regards,
    Ganga

    Hi,
    You can try this enhancement: MEREQ001
    The exits are:
    1)EXIT_SAPLMEREQ_001:-include name is ZXM02U01.
    2)EXIT_SAPLMEREQ_002:-include name is ZXM02U02.
    3)EXIT_SAPLMEREQ_003:-include name is ZXM02U03.
    4)EXIT_SAPLMEREQ_004:-include name is ZXM02U04.
    5)EXIT_SAPLMEREQ_005:-include name is ZXM02U05.
    6)EXIT_SAPLMEREQ_006:-include name is ZXM02U06.
    7)EXIT_SAPLMEREQ_007:-include name is ZXM02U07.
    8)EXIT_SAPLMEREQ_008:-include name is ZXM02U08.
    9)EXIT_SAPLMEREQ_009:-include name is ZXM02U09.
    10)EXIT_SAPLMEREQ_010:-include name is ZXM02U12.
    Regards,
    Viji

  • Material bapi custom field change to be logged in change document

    Hello all,
    I have just added a custom field to MARA table (materials), and updated it successfully via BAPI_MATERIAL_SAVEDATA.
    I would like now to log changes via change documents but problem : after having changed value from "A" to "B" for example, I don't see the changes (to do this, I call function CHANGEDOCUMENT_READ with parameter OBJECTCLASS = "MATERIAL" and get results from returned EDITPOS parameter).
    What is surprising me is that I can see changes of other standard and custom fields (this was done by other people in my company 2 years before but I don't have any trace what they did).
    Do you have any idea what customizing need to be changed or what else need to be done, to log changes of new custom fields into change documents?
    Thanks a lot.
    sandra

    In this transaction, there is nothing related to fields; there are only objects (like MATERIAL) and tables (like MARA).
    I can't see anything which makes the difference between our 2 custom fields MARA-ZZCOLLANA (which is logged in change documents) and MARA-ZZSSCOLL (which is not logged in change documents).
    For info, my SAP version is R/3 46C.

  • How to avoid purchase req and stock transport order to take part in MRP.

    Please suggest how to avoid purchase req and stock transport order to take part in MRP.

    hi,
    check the settings for the MRP type...there you need to show which doc will be taken into considerations...
    SPRO >> MM >> CBP...
    Under CBP check for the MRP settings where it is placed(check under master data settings)...and check for the indicator for PR's and STO's release orders under tab "Additional external req. in the reorder point planning"..
    Regards
    Priyanka.P

  • Pricing Redetermination when custom field changes ON Additioanl data B Tab

    Hi All Experts,
    I have added new custom field(ZZ_STCEG, ZZ_ASTCEG and ZZ_MSTCEG) on Addititonal data Tab B. Before that i added those fields in KOMP(ZZ_STCEG) and VBAP(ZZ_STCEG, ZZ_ASTCEG and ZZ_MSTCEG).
    I have a function module which gives output EX_STCEG.
    Now i need to assign the ZZ_STCEG to ZZ_ASTCEG as it is determined by system. If i enter value in Manual field(ZZ_MSTCEG) this should be used for pricing and also assign it to ZZ_STCEG. (Note: But ZZ_ASTCEG should not be changed as it is automatically determined beforre.)
    I have programmed in UserExit_Pricing_Prepare_TKOMP as below.
    Call to function module(output ex_stceg)
    vbap-zz_astceg = ex_Stceg.
    if vbap-zz_mstceg is not initial.
    vbap-zz_stceg = vbap-zz_mstceg.
    tkomp-zz_stceg = vbap-zz_mstceg.
    else.
    vbap-zz_stceg = vbap-ex_stceg.
    tkomp-zz_stceg = vbap-ex_stceg.
    endif.
    But it is not working as intended. I think because Vbap_zz_Mstceg doesnot have value during pricing because we fill it after the pricing in additional data tab B.
    Please suggest me how to proceed with this situation.
    Thanks & regards,
    NarsiReddy.

    In your screen 8309, you can do like below, when you hit enter in the field the princing will be recalculated:
    FIELD VBAP-ZZ_STCEG MODULE zm_blablala ON REQUEST.
    MODULE zm_blablabla.
    * This standard perform will do the pricing redetermination
         PERFORM preisfindung_gesamt USING 'C'.
    ENDMODULE.
    Regards,
    Felipe Simionatto

  • Custom field changes in Project 2010

    Is there a last-modified-date indicator in one of the databases to indicate when a custom field was changed? For example, I want to know when a custom field called project-phase (not workflow) has changed from one value to the next within a PDP. 
    The purpose is to produce a report that indicates the progression of a project from one phase to the next (plan-analyze-design, etc.).

    this question is closed - but for what you asked for the basic query provided  gave you the custom field modified date which would be more precise then the project modified date - 
    The below query will get you the information you want
    YOU put in the project GUID  OR the GUID of the Custom Field and this will return the tasks and project name it will also show you the difference (at least it did in my DB) the project modified data versus the task/custom field modified date which is
    also what you asked for...
    USE ProjectSevrerDraft
    SELECT
    mscf.MD_PROP_NAME as "Custom Field",
    mstcv.MD_PROP_ID as "MD PROP ID - can remove",
    proj.PROJ_NAME as "Project Name",
    proj.MOD_DATE as "Project Modified Date",
    mst.TASK_NAME as "Task Name",
    mstcv.CREATED_DATE as "Task Created Date",
    mstcv.MOD_DATE as "Task Modified Date"
    FROM MSP_TASK_CUSTOM_FIELD)VALUES mstcv
    JOIN MSP_PROJECTS proj
    ON mstcv.PROJ_UID=proj.PROJ_UID
    JOIN MSP_TASKS mst
    ON mstcb.TASK_UID=mst.TASK_UID
    JOIN [ProjectServerPublished].[dbo].[MSP_CUSTOM_FIELDS] mscf
    ON mscf.MD_PROP_ID=mstcv.MD_PROP_ID
    -- You can select either below un-comment out the '--'
    -- And insert what you want - the project or Custom field
    -- GUID will help. The PROJ_UID is found under MSP_PROJECTS
    -- THE MD_PROP_ID is found under the published database in
    -- the MSP_CUSTOM_FIELDS table
    --WHERE mstcv.PROJ_UID =' GUID OF PROJECT'
    --WHERE mstcv.MD_PROP_ID = 'GUID OF CUSTOM FIELD'

  • Tracking Custom field changes

    Hi Experts,
    I need to find when was a value being inserted/updated/deleted for a custom field in a database table.
    E.g. if in KNA1 I have a custom field ZZTEST...
    I need to know when was this field last used i.e. when was the last time that a value was inserted/updated/deleted from this field.
    Is there any standard program/function module which will help us solve this issue?
    Thanks!

    U can track changes of the custom table using change documents.
    Let me explain you tracking process in deatil so that u can look further in that direction. I am taking example of KNA1 table. Only those fields of the table are tracked through change documents for which  change document is checked at data element level. U can find change document check box at data element level under further characteristics tab.Now for all fields of custom table ( z table) for which u want to track changes u need to check this box.
    All the change data for standarad table tracked through change documents is stored in tables CDHDR & CDPOS.
    CDHDR -> Change document header
    CDPOS--> Change document items
    All data is stored w.r.t OBJECTCLAS. OBJECTCLAS groups various tables of similiar business process for tracking changes.
    Whenver u make any changes in fields marked with change document ................. a change number for the table w.r.t to  OBJECTCLAS is generated in CDHDR table.Using this change number and OBJECTCLAS  we can extract all change details from CDPOS table.
    i.e  VERKBELEG is OBJECTCLAS for all SD related tables(vbak ,vbap,vbuk etc...).
    U need to do following actvities to track changes:---
    1>  Got to custom table and at data element level check the box change document.
    2> Go to SCDO and create the custom OBJECTCLAS for ur table.
    hope u understood basic concept behind it and will look in this direction to solve ur problem.

  • Custom field update in Purchase Requisition Final Release

    Hi,
      We have PR release strategy at Item level.
    In PR table EBAN include I have added new field as ZZREL_DT (for final release date), This Field I want to update when final release will get triggred for the PR item.
    For updating this custom field I have try with  Enhancement 'M06B0002' but system is not updating  the value in new field , and as in BADI 'ME_REQ_POSTED', the IM_EBAN is an importing structure ,system is not allowing to change the value if we implement this BADI.
    Is there any user exit or BADI, to update this custom field, I want to update the system date when user releasing the PR item with ME54N or ME55 transaction.
    Regards,
    Zafar

    Hi ,
    Try with create new tab in PR item level, add field in custom tab example Final release Tab.
    Try to fetch data from EBAN table when final release happened ( based on status ) the date will update in this table. I hope this is helpful.
    Use user exit to create custom tab and custom field 
    enhancement MEREQ001 : check this enhancement.
    user exit EXIT_SAPLMEREQ_0*
    I hope it is helpful

  • Add a custom-field in the table MARC and manage it in MM01/MM02/MM03

    Good day to all of you!
    I have this task: To add a custom-field to the table MARC. This custom-field will be managed through the MM01/MM02/MM03 transaction as follows:
    In the Basic Data 1 or Basic Data 2 the custom-field data will be added. Let's say the field is MATNR OBSOLETE.
    I have searched and implemented the things in customizing: Made a copy of function group MGD1, added the field on the screen.
    MY PROBLEM! How to manage it??? When the user enters MM01/MM02/MM03 and update this field, the field should be updated in MARC.
    1. I am not sure that this custom-field should be on Basic Data1 or Basic Data2.They want it at plant level.
    2. How to manage the data transfer from SAP Standard Program and my Custom Function Group.
    PLs: Do not paste me link to sap technical site with that example, because there takes the custom fields and UPDATE a CUSTOM TABLE. I need to update MARC!
    All the documentations i have read until now tell you how to add the field, ONLY the first part of the SOLUTION.
    Any help, pls?
    Good day and thank you!

    Hi Alex,
    In which way you are trying to update that custom filed. Have you written any logic in EXITS/BADIS?
    http://pavelgk.pbworks.com/f/6729224-Implement-Screen-Exit-for-MM01-Adding-New-Fields-in-Screen.pdf
    and
    Just read the OSS note mentioned earlier.
    Symptom
    You want to integrate customer-specific fields in material master maintenance.
    Other terms
    SAPLMGMM, RMDATIND, ALE, CI_MMH1, EXIT_SAPLMGMU_001 
    Solution
    To add customer-specific fields to an existing material master table (such as MARA or MARC) , you can proceed as follows as of Release 3.0C:
          1. Use an append structure to add the fields to the required table in the Dictionary (this is not a modification; for details, see the SAP document "ABAP/4 Dictionary"). In Release 3.x, the length of the field names must be the same as  the standard five character fields. This is necessary because of dynamic assignments. As of Release 4.0A, the lengths of the field names can be longer than five characters. If the changes of the fields should be recorded in the change document and taken into account during ALE distribution, set the 'Change document-relevant' indicator for the corresponding data elements. For table MARA in Release 3.x, you must also enhance the database view MARU because the database changes are carried out using this view. This small modification is no longer necessary as of Release 4.0A because the database view MARU is enhanced automatically when you enhance table MARA or the include EMARA (which is the data part of table MARA).
          2. Enhancing online maintenance in customized material master maintenance:
          Define a subscreen with your customer-specific fields in a customer-specific function group created as a copy of the standard function group MGD1.
          In Customizing, assign this subscreen to a maintenance screen using the "Copy customized material master" function. For details, see the Implementation Guide (IMG). As of Release 4.0A, program COPYMGD1 is available. You can use this program to create customer-specific function groups as required. This program is also incorporated in the Customizing function 'Configure customized material master'. Ensure that each field of the subscreen has a field statement in the flow logic, otherwise the data is not transported correctly. You can use subscreen SAPLMGD1 2002 as an example.
          If you want these fields to be subject to standard field selection, you must add new entries for them to the central field table for material master maintenance (T130F): 
          Application examples for standard field selection:
          The field is mandatory and is to be flagged with a "?".
          The field belongs exclusively to the purchasing user department. Purchasing data and MRP data are both contained on one screen. However, the MRP controller is not to see the purchasing data.
          The following data is required for each field:
                a) Field name        (T130F-FNAME)
                b) Field selection group (T130F-FGRUP)
                Here, you should use a standard field group if the customer field is subject to the same field selection as the standard fields of the standard field group. If it is not, use a customer-specific field group.
                You must then check and, if necessary, modify the attribute of the field group using the function "Maintain field selection for data screens" in Customizing under "Logistics Basic Data -> Material Master".
                Field groups 111 through 120 that are not used in the standard system are reserved as customer-specific field groups. As of Release 3.0F, additional customer field groups are available. (For details, see the IMG).
                c) Maintenance status (T130F-PSTAT)
                List of the user departments that may maintain the field. You can display possible values by using the input help for the maintenance status field in the Customizing activity "Configure Material Master" when maintaining logical screens.
                d) Reference        (T130F-KZREF)
                This indicator must be set if the field from the reference material should be proposed during creation with reference.
    Note: You cannot yet use Customizing to enhance table T130F; you can use only transaction SE16 (Data Browser) or transaction SM31. Future releases will include a separate Customizing function for maintaining customer-specific fields. See Note 306966. By implementing this note you can add entries to table T130F within Customizing. This type of maintenance is possible as of Release 4.5B.
    You may change the entries for standard fields only with regard to the reference data and field selection group. Changing other data for standard fields constitutes a modification. Therefore, you cannot use the Customizing function "Assign Fields to Field Groups" to change this data.
    In addition, you must not add new standard fields to table T130F.
          3. If you want to maintain customer-specific fields using data transfer by direct input or via ALE distribution, proceed as follows:
          Add the fields to central field table T130F (see above).
          Add the customer-specific fields to the data structures for the data transfer (for example, BMMH1 for the main data).
          Also, add the customer-specific fields to the tables in which the incorrect data is stored during direct input. These tables have the same name as the corresponding master data table and also have the suffix _TMP.
          For example: If you add customer-specific fields to table MARA, you should add the same fields to table MARA_TMP.
          If you use ALE, you must also add fields to the IDoc. To process enhanced IDocs, you can use enhancement MGV00001 with customer exit EXIT_SAPLMV01_002 for creating the IDocs and customer exit EXIT_SAPLMV02_002 for posting the IDocs.
          Prior to Release 3.0E, enhancing structure BMMH1 constitutes a modification. In this case, you must add the new fields tot the end of the structure before the last field (SENDE = record end indicator).
          As of Release 3.0F, structure BMMH1 contains the customer include CI_MMH1, which is part of the enhancement MGA0001. Here, you must proceed as follows:
                a) Add the customer-specific fields to include CI_MMH1.
                The names of the fields in CI_MMH1 must be identical to those of the corresponding fields in material master tables MARA, MARC and so on.
                Important: The fields must be CHAR type fields. Therefore, create CHAR type data elements whose lengths are identical to the output length of your fields in  table MARA and so on. Use these data elements in include CI_MMH1, but use the field names from table MARA and so on.
                b) Activate include CI_MMH1.
                c) If you have not used customer structure ZMMH1 before, create it as a copy of structure BMMH1 and delete the standard fields that you do not require. You are not permitted to delete field STYPE and include CI_MMH1 when doing this. If you have already used structure ZMMH1, add include CI_MMH1 to it.
                d) Activate structure ZMMH1. This also adds the customer-specific fields to ZMMH1.
    Run program RMDATING. This program generates routines which are supplied to your customer-specific fields from the input file. As of Release 4.5A, you also need to activate the routines/function modules generated by program RMDATING (especially, the MAT_MOVE_BMMH1_XXXX modules). Details about this subject (especially the procedure when using customer structure ZMMH1) are described in the IMG for transferring the material data under item 'Maintain Transfer Structure'. Also, check the declaration of structure WA in program RMMMBIMC to see whether it is declared with sufficient length. If necessary, enhance the declaration (for the time being, this still constitutes a minor modification).
    In addition, lengthen domain DI_DATA with CHAR 5000. As of Release 3.1H, this has already been done.
    Important: When using customer-specific fields, you can use only structure ZMMH1 to transfer the data. Otherwise, after the next SAP upgrade which contains new standard fields in structure BMMH1, the input files no longer match. If you want these new standard fields to be transferred, add them after your customer-specific fields (the order of the fields in structure ZMMH1 does not need to be the same as the order of the fields in BMMH1).
    If you want foreign key dependencies or fixed domain values to be checked, or another check for a customer field, this is possible up to and including Release 3.0D only by modifying the corresponding check function modules. As of Release 3.0E, you can use function exit EXIT_SAPLMGMU_001 (SAP enhancement MGA00001) for these purposes.
    If you want to use engineering change management to schedule future changes for your customer-specific fields or you want to use the 'Display at Key Date' function, execute program GENERATE in addition. This program generates the necessary assignments for interpreting the change documents. With regard to engineering change management, you must read Notes 60281, 60973, and 48962.
    To date, it is not possible to integrate customer-specific tables in material master maintenance without making a modification. However, you can create customer-specific development objects containing the essential additional logic. You can then integrate these development objects in your system as part of only a minor modification.
    check this link. It may helps you to solve your issue.
    Thanks
    Sravan

  • Custom field in PO header tab and its editable status

    Hi All,
    I have added an input field in the PO header (Customer Data) tab.
    The same field has been appended in the EKKO table.
    The update as per user's entry in PO is getting done in database table.
    The field will get grayed out for ME23N tcode and will be editable for ME21N and ME22N.
    The logic has been written in the PBO section.
    Now, within the tcode ME23N, user has option to get into change mode by pressing F7.
    Once user clicks F7, the PO gets into change mode, but the custom field will be still in uneditable mode itself.
    There are couple of other custom fields are in the same tab. They get into change mode with F7, but this alone remains un editable.
    How to make it editable in this scenario???
    Regards
    Pavan
    Edited by: Pavan Sanganal on Dec 26, 2011 6:56 PM

    HI Pavan,
    so only one custom field will not update in update mode after clicking f7 , so what happend exactally when user clciks on f7 the field properties are changed in to editable mode, in module pool program we can change field properties using internal table SCREEN , so loop the screen check this input field properties , like
    loop at screen .
    if screen-name = 'custom_field'.
    input = 'x'.
    endif.
    endloop.
    Regards
    Siva

  • Customer field Not shown in ME21n and ME22N

    Hi,
    While creation ME21N and change ME22N we are unable to get Customer field in Delivery address tab of the PO, We are getting Address and Vendor (Sc Vendor) fields in Delivery address tab , but customer not able to see.
    The Customer field we can seen through ME23N.
    We have cross check screen layout for ME21N and ME22 and NBF here in all cases Customer field is Optional.

    Hi,
    Please check screen layout for AKTH & AKTV.
    Regards
    Subbu.

  • Replication of Custom Fields from CRM to ISU and Vice versa

    Hi Experts,
    We are working on adding Z fields on BP level. For this how does the replication of the values takes place from CRM to ISU or vice versa. What are the middleware enhancement we need to do in CRM side or in the ISU side. We would add the fields on web UI crm side by AET but at ISU side how we need to do that and how would the field values replicate in both the system.
    A approach for adding BP custom fields in CRM and its interaction with ISU and vice versa would be appriciated.
    Thanks,
    Mayur

    Excuse, you may enter more in detail?
    I have created a custom field on BP using the AET would now like to replicate this custom field in BP also in ISU.
    I can do all this using the EEWB, but I would avoid it, since, in ISU we already have custom fields on BP, I just can not link them with CRM.

  • Price differece between purchase req and PO for free text purchase

    Hi there
    Has anyone found a good solution for the following problem. 
    A free text purchase requisition item is created with a value = x.  The buyer goes out to quote (not using SAP RFQ - manual) and comes back with a price change.  The buyer creates the purchase order referencing the purchase requisition, but they need to change the value to x+10. 
    The client wants to stop the purchase order been created if the value is above a certain percentage.  The standard settings in the system are for material values.  Does anyone know how to extend this to a short text item on a purchase requistion?
    Thanks
    Roz

    Hi,
    This is not possible to achieve in SAP standard functionality.
    You can do one thing, keep Price field for the PO Document type of Text Purchases as display, which will not allow user to change the price for Text POs.
    Use Release Strategy for Purchase Requisitions and keep changeability for the Release indicator as "4" and % Changeability as 10%. And ask user ro change the price in ME52N only instead of changing it in PO. If it will increase more than 10% the PR Value then system will reset the release and this PR needs to be released again.
    If it is not acceptable then you can try it with user exit "MM06E007" - Change document for requisitions upon conversion into PO

  • Purchase Req and Goods Receipt (ESS) question

    Hi,
    My client has ECC 6 and EP 7 in the landscape. I am implementing Employee Self Service portal. It looks like standard Purchasing Requisition and Goods Receipts iviews (ESS package) are pointing to SRM. We are not implementing SRM here. Is there any way I can use these iviews pointing to ECC (probably ME51n, MIGO?)?
    Do I have to have SRM in order to use these standard iviews? Is there any standard iviews available for ECC purchase requisition?
    If you implement Purchase Requisition using ECC instead of SRM, what is the licensing impact? Client has purchased the license for Employee Procurement Self Service.
    Another question is, Is there any standard iview for Travel & Expense approval? I don’t find it in MSS.
    Thanks,
    Umesh Garg

    HI Horny,
    Can you use the Following Tables:
    S039 - > LETZTABG - Date: last (i.e. most recent) goods issue
    EKPO -> EBELN - Purchasing Document Number.
    You can create View by using these two tables (Material Number is the Common) and uploade the data.
    Hope this will be helpful for your question.
    Thanks
    Rajesh
    Message was edited by:
            rajesh

  • Purchase Req and Goods Receipt

    My client has ECC 6 and EP 7 in the landscape. I am implementing Employee Self Service portal. It looks like standard Purchasing Requisition and Goods Receipts iviews (ESS package) are pointing to SRM. We are not implementing SRM here. Is there any way I can use these iviews pointing to ECC (probably ME51n, MIGO?)?
    Do I have to have SRM in order to use these standard iviews? Is there any standard iviews available for ECC purchase requisition?
    If you implement Purchase Requisition using ECC instead of SRM, what is the licensing impact? Client has purchased the license for Employee Procurement Self Service.
    Another question is, Is there any standard iview for Travel & Expense approval? I don’t find it in MSS.

    ok

Maybe you are looking for

  • How do I view the files on my flash drive?

    I made the switch from PC to Mac and I bought (Dec 2011) a new Macbook Pro; I put all of my files (from PC) on a flash drive and now I want to open/save them on my macbook.  Please explain how I do this. (First time Mac user). Thanks.

  • Nokia 6220c. Problems with Gmail.

    I'm having problems running Gmail on my 6220c. I've downloaded the application for the 6220c and installed it successfully in the "My Own" section of Applications. When I try to open Gmail I get the following error message; "java.lang IllegalStateExc

  • Drop-down list to trigger instance manager

    I may have bitten off more than I can chew with this one, but I have two pages. One comprises a checklist of Y/N/NA drop-downs; the other page has a repeating table row. If the drop-down selection is N I want the Instance Manager to trigger a new row

  • E63 email notifications.

    Hello, I'm receiving me email through the "Email on 3" service from 3 mobile and everything had been working perfectly until today when all of a sudden I stopped reciving the regular email notification on my home screen. I still get an audio alert th

  • Unable to open UWL iView!

    Hello, I did all the configurations for UWL. I am using user mapping with the same user ID (both portal/R3). I get this message when I open the UWL iView... Unable to perform the request. Try again. If the problem persists, inform your system adminis