Custom field in XK05-Block/UnBlock Vendor details

Is it any way possible to capture blocking period(date) of a vendor in XK05 along with reasons description besides block function?

Dear Hamsitha Reddy,
When you go for xk05 first you have give your vendor number & company code then press enter
Then you give some relavant fields 1.under posting tab you can select SELECT COMPANY CODE 2. under block for quality reasons tab , SELECT BLOCK FUNCTION 99 (Total Block) then save.
Try any posting use this vendor number Example : F-43.... Then its will give error message vendor xxxxx Blocked for posting
Hopes It's helpfull.
If you satisfy this Answer please give me points
Thanks & Regards
shankarsap

Similar Messages

Help bapi to block/unblock vendor (XK05)

Friends,
Does anybody know what bapi can I use to block and unblock a vendor for purchasing and how to use it ?
thanks,
Glauco

Hi,
There is one fm to unblock vendor VENDOR_PURCHASING_DEBLOCK.
Also, take a look fm VENDOR_BDCDATA... it might be useful as well..
Do a where used list on VENDOR_BDCDATA if you want to see how it is to be called..
Sri
Message was edited by: Srikanth Pinnamaneni

Is it possible to add a new field in Block/Unblock vendor screen?

Hi Experts,
Kindly any one advise is it possible to add new field in xk05 screen as shown in the attached screen.If possibe,please advise the possible steps
to add this new field.
Thanks & Regards,
Anusha

Hi Pavan,
Thank you for your reply.I have searched for user exits there is no screen exit of xk05 and I put a break point in CL_EXITHANDLER method and I found VENDOR_FIELDSTATUS BADI only for this screen.So,there is no BADI or user exit to add a new field to this screen.So,how to add
a new comment field to this XK05 screen.
Rgds,
Anusha

Missing customer fields in Coding Block

Hi,
I used OXK3 to create some customer fields and they could be seen in table BSEG and structure CI_COBL and CI_COBL_BI. but when I could not find them in 'Include fields in Totals Table (FAGL_GINS)' . and I could not find and use them in subscreen creation neither. Did I miss something? Could anybody help me?
BR,
Johnny

Did you read 1854555 - Adding a new customer field to the FAGLFLEX* table and 923687 - NEWGL: Fields in CI_COBL and FAGLFLEXT .
Regards,
Raymond

Automatic blocking and deletion flag for temporary unblocked vendors/custom

Hi All,
Can you please help me IS there any Standard Reports for the Follwing,
*"automatic blocking and deletion flag for temporary unblocked vendors/customers in Master Finance SAP machines"*.
Please reply me as soon as possibly.
Thanks & Regards,
Pavithranad.
Moderator message: please research before asking, do not assign higher urgency than normal.
Edited by: Thomas Zloch on Mar 3, 2011 2:43 PM

In XK06, flagging Vendor for deletion, I get warning "vendor xxxxx has open items in company code xxxx". Does this mean open Invoice Items, pending payment in FI? Since this is just warning I can hit enter and go ahead and save.
- YES YOU ARE RIGHT. IT CAN ALSO INCLUDE OPEN PO.
But, I can come back to XK06 and UNflag this same vendor for deletion? How would it affect the open items/POs...etc?
- THAT'S WHY THE MESSAGE IS AN WARNING AND NOT AN ERROR. (My Opinion)
Does basis has to do some sort of execution in order to actually delete the vendor master from the database? Would basis get a error when there are pending open items for vendors flagged for deletion?
- NOT RECOMMENDED. ANY DATA CAN BE DELETED THOUGH. IF YOU ARE ON ECC 5.0 OR ABOVE AND USING SE16N TO DELETE, YOU WILL NOT GET AN ERROR.
What's the advantage of using XK05 (blocking/unblocking) over XK06 (flagging/unflagging for deletion)?
- NOT SURE IF THERE IS ANY ADVANTAGE.

Adding custom (z) fields to assignment blocks...

We are running SAP CRM 7.0. We are using the opportunity module as well as "Create Follow Up" (Sales Order / Quotation) so that you have a one to many relationship (1 opportunity may contain many sales orders). I have 2 custom fields inside the Sales Cycle (Quotation) module "Actual Sales Order Value" and "Current Points".
What I am trying to do is take these 2 custom fields and add them to the assignment block called "Linked Transactions" in the Opportunities module. But when I look at all the available fields for this assignment block these 2 custom fields are nt available.
I do not see any way of adding these 2 fields to this assignment block. The only thing I see is "Create NEw Field". But I do not want to create a new field I just want to reference 2 fields from the Sales Cycle module inside of this assignment block.
Does anyone knowif it is possible to add 2 custom created fields that are i the Sales cycle module to add them to the opportunities assignment block that is called linked transactions ?
Thanks,
Jon

Duplicate thread.
Re: Add custom fields to assignment block
Please close.
Rg,
Harshit

Blocking Purchasing Vendor(TC :MK01 & MK02)

Hi All,
Can anybody help me how to block a Purchasing Vendor(MK01 & MK02) using Change Document Procedure.
I found the Business Object LFM1 & change document Object KRED .
i copied LFM1 into one custom object(ZLFM1) & created a Method & Event for blocking the vendor.
in SWEC, i linked the ZLFM1 & KRED.
But it is not working.
Please can anybody help me to solve my problem.
Regards
kalyan.

Hi Rob,
Thanks for quick reply.
My requirement is to block a Purchasing Vendor (MK01 & MK02) when ever a new vendor is created or changed.
I am doing the same with user exit & BTE.
I am not getting the vendor number when I created a new vendor when save document triggers. Because FM NUMBER_GET_NEXT is executing after the user exit(EXIT_SAPMF02K_001) and Before BTE 1420.
So I am taking EKORG form user exit & passing the same to BTE.
Now in the BTE I am having both LIFNR & EKORG.
In the BTE I am using FM SWE_EVENT_CREATE to trigger the workflow.
I am using a Custom business object to block the vendor.
But if it good practice if we can do the same thing using change document procedure.
So I found the Change document KRED. But in the KRED EKORG is not the key field.
So I copied the business object LFM1 and created a custom method & event to block the vendor. Since I dont have any standard object for blocking the purchasing vendor.
So I am doing the following steps.
In TC SWED
I created an entry for KRED with LFM1 is the leading table in the change document.
I created an entry in SWEC as change document object as KRED and business object as Custom business object.
But when I am executing MK02 it is giving following message
Object does not exist
Message no. OL 826
Diagnosis
You tried to create an instance of the object type YR_LFM1 with the key0000000105. No instance of this kind exists.
If check the above message(red color) we are having only LIFNR as 0000000105 & there is no EKORG. So here Key field is not creating properly.
How can we debug the change document object?
Thanks & regards
Kalyan.

Problem in custom fields in mm02/mm03

Hi folks,
i want to add the custom fields in mm01.iam able to add and update database.but iam facing problem in when iam checking the particular material in mm02/mm03.the custom field data is not correctly.for every material the last custom field data is showing. in database it is updating correctly but in mm02/mm03 it is displaying incorrectly.
By the following code i can able to display the data in mm02/mm03.but my problem is the last created custom field(model) data is showing for all the materials when iam checking in mm02/mm03.
here my custom field is "MODEL"
for eg matnr-10 model -xx.
matnr-20 model-yy.
if iam checking in mm02/mm03 for matnr-10 model-yy it is displaying.in database it is updating correctly.
can u please tell me how can i write a code to select the custom data(model data) for that particular material.
Module get_data.
if sy-tcode = 'MM02'.
select single model into mara-model from mara
where matnr = mara-matnr.
elseif sy-tcode = 'MM03'.
select single model into mara-model from mara
where matnr = mara-matnr.
loop at screen.
if screen-name = 'MARA-MODEL'.
screen-input = 0.
modify screen.
ENDIF.
endloop.
endmodule.
Thanks in advance,
Neelu.

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.
Regards

Add fields in "customer fields" at item level

Hi experts.
Please i need a help.
Im using the SAP CRM 5.0 win client.
I will use the EEWB method to add new fields at the item level (CRMD_CUSTOMER_I). I believe that these fields will appear in the "customer fields" tab, but this tab isnu2019t displayed inside item details.
Why its can be happen?
Is some config. missed?
Thanks in advanced.
Daniel

Hi Ratish
First i wanna thank you for the reponse.
In fact i didnt execute the EEWB yet.
My question is, the tab "customer fields" isent displayed inside the item details so after that i run the EEWB and check "item" to add the fields, the tab "customer fields" will be displayed automatically?
Thanks so much, i have added to you some points.
regards.

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

User Exit to add custom field in Component Screen

Hi Friends,
I searched alot but could find exit to add custom field or tab in material component detail screen for SAP 4.7. Please let me know if there is any exit or workaround possible.
Thanks,
Raj

BADI is available to create custom field in material component , but it is available as of ECC 6.0 EHP3 , not sure about 4.7

Is doing configuration for FB60 using customer field a core mod?

Hello,
For our project, a customer field 'ZZAPPROVER' was added in FB60 transaction code.
It is possible through configuration through the following path:-
SPRO --> Financial Accounting (New) --> Financial Accounting Global Settings (New) --> Ledgers --> Fields --> Customer Fields --> Edit Coding Block --> Customer-Defined Account Assignments --> Customer Include Structure
This basically added the customer field 'ZZAPPROVER' to the include structure CI_COBL.
The important point to note here is that it adds to BSEG table too.
Now the business is asking whether this is considered as a core modification to SAP.
Can anyone update where it is a core mod or not, and if there is any documentation to prove this?
Your comments are highly appreciated!
Regards,
Sanjiv Janardhanan

Hi,
The adding of additional Customer field is available from ECC 6.0 onwards. This is a standard functionlity to enable the customer to add their own fields for better reporting. But SAP cautions that it is better to take backup before doing this addtioin. No posting transactions shall be performed while you are including the customer field. SAP recommends using the u201Clightu201D mode. For this, you only need to make the following entries so that all necessary changes to the dictionary and to the tables are performed automatically in the background:
●      Collection (package)
●      Field name
●      Field description
●      Data type
Character field (CHAR)
Character field with digits only (NUMC)
Trust this helps much!
Cheers!

Fetch Vendor block/unblock date and time information in Transaction XK05

Hi ,
When user blocked to vendor using transaction XK05,This data stored in the table CDHDR (bloked Date and time).
My quostion is how will we fetch the bloked DATE and TIME from CDHDR table( i mean which condition i need to fetch).
This table have the blow key fileds .
1) OBJECTCLAS       Object class
2) OBJECTID             Object value
3) CHANGENR          Document change number
Could you please help us to resolve this.. << Please do not offer rewards >>
Thanks
Satya.
Edited by: Rob Burbank on Jun 24, 2010 10:44 AM

In Development, repeat the block process, then go find what you just put into table CDHDR with SE11 or 16...a little innovation and initiative often allows one to discover precisely what is needed, if you'll pardon an admonition from an old programmer )

Mass Vendor Deletion and posting Block unblock.

Hi All,
I have done the mass deletion flag and posting block of vendors ate P.org and Co.code level through t.code-XK99.
I want to retrive my changes and vendor shuold active again instead of populating a warning message.I am aware of T.Code-XK05 but i tried it through T.Code-XK99 however i am not able to unblock those vendors.
could anyone let me know were i am ,missing.
Regards,
Gaurav Surana

Transaction MASS > LFA1 is same as in XK99
XK99 should work in your case. Please check that you are selecting the correct table and fields to be changed in this XK99 transaction.
Are you also getting any error message during the saving in XK99?
Regards,
SDNer

What are the different types of blocking in vendor / customer MD?

Hi,
in my firm we noticed that several customers were marked for deletion but this mark only provides a warning message once sales order is set up.
We'd like to know how to perform actual blocking of sales order / delivery / billing for customers - what should be done and how in the customer Master Record?
Same problem goes to vendors. Marking for deletion only provides a warning message once a PO is set up, what should be marked and in which transaction in order for this vendor to be blocked for PO / Goods Receipt / Invoice receipt / payment?
Would appreciate your response

Dear okit83,
There are many ways to block the vendor/customer. As above mentioned VD05/XK05 will be used to block the customer/vendor.
Apart from that we can block the customer/vendor from the same master data is self.
Go to xd02/xko2-> Extras->Block data. Here tou can block the customer/vendor from one sales area or from all sales areas pertinent to delivery,sales billing(CUSTOMER). Where as vendor allcompany codes,all purchase organizations.
Similarly you can delete the customer/vendor by using delition flags By XD02/XK02->extras->Deletion flags.
So the customer/Vendor will not be used
Please check and revert
Thanks&Regards
Raghu.k

Custom field in XK05-Block/UnBlock Vendor details

Similar Messages

Maybe you are looking for