Incompletion log at Item detail level and document type

Hi friends.
I want to create incompletion log for field Reason for rejection (VBAP-ABGRU) for particular document type how I can achieve this ?
Regards,
Chetan.

Hi
To add any field to the incompletion procedure,
Check the Incompletion Procedure assigned
- for Header - assigned to the sales document type.
-for Item - to the item category
Goto IMG-SD-Basic FUnctions- Log of Incompleteness-Define Incompletion procedure(Tcode OVA2)
Select your Incompletion Procedure - click on Fields(on the left side of screen) and Click on New Entries and add your required field.
Now check the functionality.
Thanks,
Ravi

Similar Messages

  • Two different Incompletion log in item level for one sales document type

    Hi All,
    we are using one sales document type for 5 different sales org, now we are implemented new sales org.
    pervious all 5 sales org we have setup incompletion log at item level 5 fileds.now for new sales org we need to setup out 5 fields we need to setup 3 field.
    how to maintain same sales document type 2 different incompletion log.
    i have checked in forum i found out below link.but is not matching for my requirement.
    http://forums.sdn.sap.com/thread.jspa?threadID=1433420
    Thanks,
    Kumar

    Hi ,
    Thanks for your responds.
    i will check with my ABAP  person if any thing is required i will come back to you.
    Thanks,
    kumar

  • How to show field at item detail level (purchase requisition layout)?

    Hi, gurus!
    We're trying to get field "processor" shown at item detail level (release strategy tab) when we create, modify or display
    a purchase requisition.
    We click on right button, select "Show" and get column name "Processor" in displayed columns and save layout as default,
    but that field is not visible when entering again transactions ME51N, ME52N or ME53N.
    Could anyone help us?
    Thanks in advance
    Regards,
    J Madariaga

    J,
    This field on the release strategy tab is linked to workflow.  You can maintain the "Processor" data by each release group and release code in the IMG menu path:  Materials Management -> Purchasing -> Purchase Requisition -> Release Procedure -> Set Up Procedure with Classification.'
    Here you enter a processor's entry under Workflow:
    Grp: Release group
    Code: Release code
    Plant: Plant
    Agent type: US is user
    Agent ID: UserID
    Once this is maintained, you return to the Release Codes section and enter a "1" by each Grp/Code where a workflow entry was created in table T16FW.  When you look at the release tab in the PR that has the same code as the one you created in the configuration, you will see the Workflow username (First and Last Name) in the "Processor" field.
    Hope this helps.

  • Adding a new Tab - ME22n - Item Detail Level

    Hi,
    This is a bit Urgent!
    I need to add a Tab to a TabStrip in Item Detail level, in ME22n that has a count of 12.
    Out of which 1 is custom made.
    Someone else had done this development and i can't figure out how it's done.
    Now, i am adding a 13th Tab.
    There is a Enhancement Project made in CMOD.
    Which has the component  MM06E004 added to it.
    I have added the subscreen 0201 to SAPLXM06.
    And activated the both the enhancement Project and SAPLXM06.
    In ME22n, i should be seeing the 13th Tab in the Item Detail level.
    But i can't.
    I have all together 23 fields... So i have no way but to add all the fields in a new Tab.
    Please help.
    Cheers,
    Remi

    Hi,
    There are some points which you need to keep in mind before implimenting this exit.
    First of all this is a transaction and check whether you need a selection screen ( of a program ) on your new tab which will be inserted in the transaction.
    And to create a field you need to enable one of the screens depending on your requirement.
    SAPMM06E 0101 CUSTSCR1 SAPLXM06 0101
    SAPMM06E 0111 CUSTSCR1 SAPLXM06 0111
    SAPMM06E 0201 CUSTSCR1 SAPLXM06 0201
    SAPMM06E 0211 CUSTSCR1 SAPLXM06 0211
    SAPMM06E 0301 CUSTSCR1 SAPLXM06 0301
    SAPMM06E 0311 CUSTSCR1 SAPLXM06 0311
    If you use any addditional fields you need to define these additional fields in following structures based on the requirement:
    CI_EKKODB
    CI_EKPODB
    To pass data from the PBO / PAI modules you have to enable the suitable function exit based on the requirement. Enabling these exits would pass data from / to the additional screen.
    EXIT_SAPMM06E_006
    EXIT_SAPMM06E_007
    EXIT_SAPMM06E_008
    EXIT_SAPMM06E_009
    EXIT_SAPMM06E_012
    EXIT_SAPMM06E_013
    EXIT_SAPMM06E_014
    EXIT_SAPMM06E_016
    EXIT_SAPMM06E_017
    EXIT_SAPMM06E_018
    So we can either add a additional tab at header level / item level in this transaction.
    Regards,
    Satish

  • Add an extra :Tab" on the Purchase Order's ITEM DETAIL level.

    Hi:
    Can anyone please tell me how I go about to add an additional "TAB" on the Item Detail level of a Purchase Order...??
    Thanks.
    W.

    It is not possible to add extra tab by configuration .you have to use user exit/BADI to get this .
    user exit :MM06E005 
    BADI : ME_PROCESS_PO_CUST
    consult with your abaper for developemnt

  • Item Details iView and Custom Event

    Dear experts,
    I need to implement a custom validation using a BAPI call to external R/3 system.
    I am planning to use the Item Details custom event as a trigger for my custom web dynpro and have my BAPI call there. My question is, can I do that? The reason I'm asking is because the event says it's a post-save-event. What I need to do is to prevent the actual Saving and display an error message if the
    BAPI call returns "false".
    Thanks for your help,
    Boris

    I see that there are too many answers to this thread
    OK, here is how we solved the issue. We are subscribing in a custom Web Dynpro to the Post-save-event of the Item Details iView and we are performing the BAPI call.
    Based on the result of the call we are setting a flag on the record and this flag is used as a syndication block.
    Hope that helps someone ...
    Boris

  • Error when select posting level in document type

    Hi,
    Did anyone have an experience to face the Abab run time error when select "posting level" in document type?
    The Error is : GETWA_NOT_ASSIGNED
    Short text
    Field symbol has not yet been assigned.
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_UC_ITKEY_FACTORY===========CP" had to be
    terminated because it has
    come across a statement that unfortunately cannot be executed.

    If you searched the notes, as Dan proposed (and didn't find anything relevant), and the answer to the Greg's question is positive, then I would suggest regeneration data basis and ConsArea due to data model inconsistency.
    If it doesn't not help - open customer message to SAP.
    Edited by: Eugene Khusainov on Jan 26, 2010 10:26 AM

  • Special GL indicator and document type

    Hello ,
    I 'm not well acquainted to the FI applications but I know special GL indicator and document type are two important thing on Financials .
    I want to learn for what purpose these two fields used .  Also I would like to learn interactions between FI GL and FI AR .  If you can share a detailed explanation about my questions, it will be much appreciated
    thanks in advance
    guest

    Hi,
    Special GL Indicator's you have to declere for special cases like Down payment and Bills of exchange etc..
    those tables are stored in different different tables and not in regular tables.
    Doc Type
    based on document type we will identify that Vendor Invoices , Customer Invoices , memo, JV.
    each doc type is having a seperate no range.
    FI-gl handled all GL issues.
    FI-AR handleds  all customer issues.
    we will get more help at http://help.sap.com/
    Reg
    Madhu

  • FB60 and Document Type

    Hi Experts, i need to limit the document types an user can choose on the transaction FB60, how can i do that? thanks in advance.

    HI
    Use validation for this purpose. OBB8
    Write a validation at Header level.
    In pre requisites : User Name (give here all user with operator Or")
    In check : Give Compnay code and Document type
    Create a message like " You cannot post using this document type"
    What system does is first checks the user name for ex : XYZ if it is correct, then system goes to check and checks for company code XXXX and teh doc type XX
    If these two conditions are satisfied only the system allows user to post the transaction.
    Reward if useful.
    sarma

  • Posting Key and Document type

    Hello,
    I have just detected an inconsistency in one of my SAP environment (Development).  I have an invoice posted from the SD module, document type of this invoice is RV.
    If there is a reason to cancell this invoice, the transaction used is VF11. The document type in SD for this cancellation is S1. Thereafter an FI document is generated with document type AB.
    Even though the settings in both Production and Acceptance and Developement are the same.
    I have realised that the initial document when cancelled (reversed) has an FI document RV  and posting key 11. whiles in customizing the settings for posting keys and document types are different from what has been customized. Below is my current settings.
    The posting key 01 has a  reversed posting key 12 and the document type RV has a reverse document type AB. This customizing is in correct in SPRO.
    Transactions : OB41 and OBA7
    Can anyone help on this....
    Thanks
    Elvis

    Hello,
    Did you verify whether AB document type in OBA7 is marked in "Account Types allowed" the Customer checkbox?
    If not, maybe that is why it is not selecting AB as the reversal document type for RV, even though it is set up in RV document the AB document type as reverse document type.
    Other than this (if the mentioned above doesn't solve your issue), I would say there should be any user-exit that can be changing the document type, according to some specific business rule of your SAP client or even a substitution.
    I hope it helps you.
    Regards,
    Daniel.

  • Regarding Delivery and document type

    Hi Gurus,
    I copied both the delivery type and document type from NL and UB and I also assigned delivery type and checking rule to the supplying plant in SPRO- LE - MM- PUR- PO - set up STO. and also assigned the Document type in SPRO- LE - MM- PUR- PO - set up STO assign doc type, one step....  
    But when I create the STO the system issues a warning message that
    Doc. type YUB should be used for suppl. plant XXXX and receiving plant XXXX
    Message no. 06674
    can you please give me some suggestions
    Shane

    Hi narayan,
    I am working with INTRA company STO and I have checked with the config what i have did again and now I can get the shipping tab.............. only thing is before I have forgot to assign the Issuing storage location in the transaction process. So now i can create  a STO.
    Now I am not sure how and where we need to make changes so that the process doesnt ask for Issuing storage location information and still create the STO between two plants in a same company.
    Thank you for your responses. They really helped me in figuring where exactly i am going wrong
    Shane

  • SAP Easy DMS - Link between Document Area and Document Types

    Deat Friends,
    Is there a transaction code or a customizing available to link the Document Area and Document Types??
    For example: Document Area (DMS) is linked with Document Type (DRW)
    Thank you,
    Sri

    Hello Chandu,
    We are trying to create a documents via TCODE: CVO1N
    One of the entry we need to populate is the "DOCUMENT TYPE" to create a document. If, we enter the Document Type = DRW, we are not able to see our custom Storage Category while attaching/Check-in a document.
    Where as, If, we enter the Document Type = DMO, we are able to see our custom Storage Category while attaching/Check-in a document.
    I see that the Document Type = DRW is linked to Document Area = DMS
    Similarly, the Document Type = DMO is linked to Document Area = FILESYSTEM
    My question is, Is there a transaction code or a customizing option available to link the Document Area and Document Type?
    Thank you,
    Sri

  • Message No delivery type defined for supplying plant BP01 and document type

    Hi all,
    I am trying to create a purchase order with a BP01 supplier and the BP02 division but I get the following error message No delivery type defined for supplying plant BP01 and document type.
    When I create a PO with a BP02 supplier and the BP01 I do not get any message.
    How can I fix it ?
    Thanks
    Regards
    Pierre

    1)Create one Customer for Supplying Plant Sales area and assign this Customer no with Receiving Plant in OLME---> PO -
    > Set up STO -
    > define Shipping Data for plants. and maintain the same sales area in your Supplying plant.
    2) In OLME---> PO -
    > Set up STO.....for your Document Type: UB and Suppying plant Combination assign Del. Type NL and Checking rule RP
    3) In OLME---> PO -
    > Set up STO...for your Supplying Plant and Receiving Plant combination Maintain Doc. Type : UB
    Make sure you are maintaining Sales View for your Material at Supplying Plant.
    4) Maintain Shipping point at, SPRO----> Logistics Execution -
    > Shipping -
    > Basic Shipping Functions -
    > Shipping Point Determination for Plants.....there for your Loading group,Shipping Condition, Shipping Plant combination maintain Shipping plant..
    Now Create STO in ME21N with Doc.type: UB at Receiving Plant.
    Then Create Delivery in VL10B from Supplying Plant...
    Then Do PGI in VL02N from supplying Plant.
    Then do GR at Receiving Plant based on Outbound Delivery at Receiving Plant...

  • In PO No delivery type defined for supplying plant and document type MRO

    Hi,
    i need urgent solution for this problem please.
    i am getting this error while creating stock transport order PO(intercompany)
    No delivery type defined for supplying plant (ex:1500) and document type MRO .
    thanks
    madhu

    Hi,
      i am getting problem in vendor master data
    1)  recently we started inter company stock transfer order (STO)process  for a vendor (delivery plant), the same vendor was using before for internal procurement for some other company code /plant, i made settings in vendor master last screen ie conditions , sales data and  control data ,and took path   from main menue selected extras-> addtional purchasing data tab to enter plant  under plant assignment tab to work STO. now we are unable to create PO for other company  and pur org(non STO company code /plant) with the STO vendor,if i remove plant under  plant assignment tab in vendor master , it is effecting inter company STO,
    i need solution for this , please help me by giving valuable solution.
    Thanks and Regards
    MM

  • No delivery type defined for supplying plant 6110 and document type ZSTD

    Hi all,
    I am trying to create a purchase order with a P6110 supplier and the 6115 plant but I get the following error message No delivery type defined for supplying plant p6110 and document type.
    When I create a PO with a 6115 supplier and the 6110  I do not get any message.
    How can I fix it ?
    Thanks
    Regards
    SAGAR

    >
    sagarn wrote:
    > Hi all,
    >
    > I am trying to create a purchase order with a P6110 supplier and the 6115 plant but I get the following error message No delivery type defined for supplying plant p6110 and document type.
    >
    > When I create a PO with a 6115 supplier and the 6110  I do not get any message.
    >
    > How can I fix it ?
    > Thanks
    > Regards
    > SAGAR
    If ZSTD is a copy of UB type PO, then you need to provide the plant number as the supplier. The delivery type can be configured in the following path
    Materials Management -> Purchasing -> Purchase Order -> Set up Stock Transport Order -> Assign Delivery Type and Checking Rule
    Copy and existing record and maintain the combination of your PO type (ZSTD), supplying plant (6110) and delivery type (NL). Leave the others the same.
    Regards,
    Aroop

Maybe you are looking for