Custom field - Next/Last Appointment?

I am looking for a solution that I have not seen referenced yet on these forums, but if this is repeating another thread, please point me in the right direction.
I am looking for a way to update two Date fields on my Account form. I want to pull the most recent appointment regarding the account and the next appointment regarding the account and make those visible on the main form.
I want this to be an automatic process running in the background, but I haven't been able to do so with workflows to this point.
Has anyone had a similar need/solution?
Dan Garland

The purpose would be to have a way to track when the last time we met with an account, and if we have a followup meeting scheduled.
Ideally this would be viewable at the organization level through an "advanced find" view by filtering for active Accounts and the Last/Next Appointment field with some kind of date range.
To address performance, is there a way to make a process like this run daily at a certain time (eg. 2am) then have the field update throughout the day ONLY if an appointment is created/completed/closed?
once again, sorry for my lack of experience - i'm happy to read on my own and find out how to do this stuff, I just haven't found something quite like this particular application yet.
Thanks in advance for any help!
Dan Garland

Similar Messages

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

Adding custom fields to BAPI_MATERIAL_SAVEDATA

With the DFPS module, SAP has added the NSNID field to the MARA table.
However, BAPI_MATERIAL_SAVEDATA makes use of structure BAPI_MARA, which does not have the same field included.
When consulting SAP about this difference, we get the answer that we can use the EXTENSIONIN tables in the BAPI to add this field. Not the best solution ever, but if it works, it works.
So I've appended our field NSNID to the BAPI_TE_MARA and BAPI_TE_MARAX structures (one with the actual type and another with the default bapiupdate type). Next I add those to the EXTENSIONIN and EXTENSIONINX tables, all exactly as shown by SAP.
When the BAPI is called, I see that the values from those tables are copied to the internal table tmara_ueb. However, no actual update takes place.
As a check, I've also added a regular MARA field to the BAPI... it gets updated without a problem. So the BAPI itself works, just not with semi-custom fields. Semi-custom because the field in the MARA is standard SAP, but we have to manually add it here.
What I've found so far is that the name of the field is of no influence (also added ZZTEST, no update either). In various posts I read about table T130F in which the field also has to be declared. The NSNID is already in there, the addition of ZZTEST does not help either.
Is there something abvious I'm missing here? Thanks in advance for the help!

Thanks for the replies Mayank and Suhas. To answer to both:
@Mayank:
Yes, both structures are declared in the code and filled. Afterwards, I assign 'BAPI_TE_MARA' to the structure part of the EXTENSIONIN and fill the valuepart1 field with the values from the declared BAPI_TE_MARA structure. That system works as it should, the values are correctly copied to the internal tmara_ueb table.
* Check field to see if there was a MARA change
ls_clientdata-document = 'TEST6'.
ls_clientdatax-document = 'X'.
* The added field we want to change
ls_bapi_te_mara-material = ls_headdata-material.
ls_bapi_te_mara-nsnid    = '222222222'.
ls_bapi_te_marax-material = ls_headdata-material.
ls_bapi_te_marax-nsnid = 'X'.
ls_extensionin-structure = 'BAPI_TE_MARA'.
PERFORM transfer_to_extensionin USING ls_bapi_te_mara CHANGING ls_extensionin.
APPEND ls_extensionin TO lt_extensionin.
ls_extensioninx-structure = 'BAPI_TE_MARAX'.
PERFORM transfer_to_extensionin USING ls_bapi_te_marax CHANGING ls_extensioninx.
APPEND ls_extensioninx TO lt_extensioninx.
<execute BAPI>
FORM transfer_to_extensionin USING    is_bapi_extensionin TYPE any
                             CHANGING cs_bapiparex        TYPE bapiparex.
DATA l_distance_characters TYPE i.
FIELD-SYMBOLS <any> TYPE any.
DESCRIBE DISTANCE BETWEEN cs_bapiparex-structure
            AND cs_bapiparex-valuepart1
            INTO l_distance_characters
            IN CHARACTER MODE.
ASSIGN cs_bapiparex+l_distance_characters(*) TO <any>
    CASTING LIKE is_bapi_extensionin.
<any> = is_bapi_extensionin.
ENDFORM.                    "transfer_to_extensionin
BDC is the very very very last thing I want to think about here... even more since - in my opinion - SAP should have updated the BAPI_MARA structure and working of the BAPI to accomodate the addition of the NSNID field.
@Suhas:
Yup, except for the material number field of course, that's the actual number as key.
The NSNID field is already available on screen, on the 'Basic Data 2' tab. So that shouldn't be a problem.

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'

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

Advanced Custom Field help. Need fiscal quarter/fiscal week.

A coworker is setting up an MS Project...project, and she asked
for some help adding a custom field that would convert the Start date field into our Fiscal Quarter Fiscal Week schema, to display as FQFW, e.g. Q1W1. I've written a formula that accomplishes this quite nicely in excel, but I've never even touched Project
until this week. Apparently it doesn't take formulas quite the same way as Excel does. I tried using the ''Switch" function in Project, and it worked, but it only accepts 14 arguments(right?), and there are obviously 52 weeks we're dealing with. Does
anyone have any suggestions? Would there be a way to do this using VBA? (I know next to nothing here as well.)
Formula in excel where A1 is the Start Date:
=IF(AND(A1>=DATE(2014,2,1),A1<=DATE(2014,5,2)),CONCATENATE("Q1","W",(INT((A1-DATE(2014,2,1))/7)+1)),IF(AND(A1>=DATE(2014,5,3),A1<=DATE(2014,8,1)),CONCATENATE("Q2","W",(INT((A1-DATE(2014,5,3))/7)+1)),IF(AND(A1>=DATE(2014,8,2),A1<=DATE(2014,10,31)),CONCATENATE("Q3","W",(INT((A1-DATE(2014,8,2))/7)+1)),IF(AND(A1>=DATE(2014,11,1),A1<=DATE(2015,1,30)),CONCATENATE("Q4","W",(INT((A1-DATE(2014,11,1))/7)+1)),FALSE))))
Any and all suggestions welcome.
Thanks.

msinnen,
You're correct, switch statements and if statements can only be nested to 15 levels. However, VBA can get you there. This macro should do what your coworker needs with the following assumptions - the fiscal year starts in January and quarters end on the
last day of the month, not the last Friday. If either or both of those assumptions are incorrect, then this macro will need some tweaking. Note: the quarter and work week designator will be written into the Text1 field.
Sub FQuartsandWeeks90()
Dim t As Task
Dim Mon As Integer
Dim Qtr As String, Wk As String
For Each t In ActiveProject.Tasks
If Not t Is Nothing Then
t.Text1 = ""
Mon = Month(t.Start)
Select Case Mon
Case 1 To 3
Qtr = "Q1"
Wk = "W" & CStr(DatePart("ww", t.Start))
Case 4 To 6
Qtr = "Q2"
Wk = "W" & CStr(DatePart("ww", t.Start) - 13)
Case 7 To 9
Qtr = "Q3"
Wk = "W" & CStr(DatePart("ww", t.Start) - 26)
Case Else
Qtr = "Q4"
Wk = "W" & CStr(DatePart("ww", t.Start) - 39)
End Select
t.Text1 = Qtr & Wk
End If
Next t
End Sub
John

Error while adding a custom field with Input help via AET

Hi All,
I need to add two custom field under Service orders at Item level in component BT140I_SRVP.
One field is required to have the input search help f4 and autopopulates the second field
I am able to add one field(not requiring help) successfully through AET .
I have created one Zsearch_help in se11 and its successfully running and Autopopulating seocnd field while I am testing it
While adding second field through AET,I need to enter following details as -
field label,search relevant ,serach help etc.
When I type the name of my 'Zsearch_help' against field search help it gives me following error
'Search help is not compatible'.
Secondly,not getting getter and setter methods for the attrributes in BTAdminI.
Last,please tell me if i create zhelp and activate it,would it automatically appear in the list on AETwhile assiging it to input field?
Please help me out.Kindly be detailed as I am new to SAP CRM.
Thanks,
Shivani

The question is answered in CRM 7.0 forum:
Getting error while adding a custom field (with input help) through AET

How to populate a custom field of a Std. SAP Tx with BAPI usage 2 Load data

Hi Experts,
For instance, I created a custom field (say, custom_field_1) on a screen of standard SAP tx(say, ME21N) by using screen exit. And in order to populate the data into it (custom_field_1), will use the Function user exits of this Tx(ME23N).
1) In next step, Where Where I have to add this field, apart from appending the same custom field in EKKO/EKPO table or any other related table; Extending the corresponding IDOC or creating a new Custom ÍDOC type? like What about BAPI?
2) If I got a text file with the data (including the data for this custom_field_1 too) and I have been asked to load it into SAP, then, I decided to use BAPI (say, BAPI_PO_CREATE or CREATE1) to create the data, So, How to handle this custom field, I mean, In which BAPI structure I have to pass this custom_field_1 data? ( Iguess, for some BAPIs EXTENSIONIN structures are provided, sorry if am wrong!)
Thank you.
Edited by: SAP ABAPer on Feb 21, 2009 7:40 PM

for example if you added field in the VBAP table then you can pass the custome field values like below
     move 'BAPE_VBAP' to lwa_extension-structure.
      lwa_bape_vbap-vbeln = lwa_final-vbeln.
      lwa_bape_vbap-posnr = lv_posnr.
      move lwa_final-yyslotid to lwa_bape_vbap-new custome field.
      move lwa_bape_vbap to lwa_extension-valuepart1.
      append lwa_extension to lt_extension.
      clear lwa_extension.
      move 'BAPE_VBAPX' to lwa_extension-structure.
      lwa_bape_vbapx-vbeln = lwa_final-vbeln.
      lwa_bape_vbapx-posnr = lv_posnr.
      move 'X' to lwa_bape_vbapx--new custome field.
      move lwa_bape_vbapx to lwa_extension-valuepart1.
      append lwa_extension to lt_extension.
      clear lwa_extension.
call function 'BAPI_SALESORDER_CHANGE'
        exporting
          salesdocument    = strcture
          order_header_inx = strcture
        tables
          order_item_in    =strcture
          order_item_inx   = strcture
          schedule_lines   = strcture
          schedule_linesx = strcture
          extensionin      = lt_extension.

Enhancement-ABAP Code-Customized Field issue

Hi Experts,
Currently I am working on the BW3.5 version. We are using the standard SRM standard extractor 0BBP_TD_SC_1 and we enhance same extractor(populate the filed through CMOD - ABAP Code) with one customized field also. We are having issue on the customized field data which post from SRM system. I have verified the field value and value is fine in RSA3 in SRM source system. But while posting into the BW(PSA itself), its loading correct & wrong value. When i check the PSA for the particular load, It looks little strange. In the PSA, I can see correct value on my first record of the same SC and then next records has incorrect value of the same SC. Currently I am using the ODS as a data target. So finally i am getting the incorrect value on the customized field.
Ex Scenario:
Ex Customized Field: ZORGID
In SRM source system RSA3 Extractor Checker value:
Shopping Card No: 100
Customized Field: ZORGID=1
Shopping Card No: 200
Customized Field: ZORGID=2
In BW posting-PSA:
Shopping Card No: 100
Customized Field: ZORGID=2
Shopping Card No: 200
Customized Field: ZORGID=2
At the same time, if i do the selective deletion of the particular Shopping Card or group of SC in BW and do the full repair, then it gets a correct ZORGID=1 for the same Shopping Card.
I strongly believe, something wrong in the ABAP code. But when we tried to debug the customized filed value in RSA3. The value is fine. so we unable to trace out the issue. Please help me to fix the code. Thanks in advance.
CMOD ABAP Code:
*Populate approver ID even though it doesn't require approval this is required to make sure BW reports have restrict access to respective Org Unit approvals only
IF l_s_bbp_sc-approver_id IS INITIAL AND l_s_bbp_sc-itm_guid IS NOT INITIAL.
CALL FUNCTION 'Z_BBP_FIRST_APPROVALGET'
EXPORTING
iv_header_guid = l_s_bbp_sc-guid
iv_itm_guid = l_s_bbp_sc-itm_guid
IMPORTING
approver_no = l_s_bbp_sc-approver_id
EXCEPTIONS
no_data = 1
OTHERS = 2
IF sy-subrc 0.
ENDIF.
ENDIF.
To ensure that the Org Unit passed in into the field
l_s_bbp_sc-zzapprov_orgunit belongs to the Actual Level 1
Budget Owner and not any other manager such as Added Approver.
CLEAR : ls_ln_approvers, l_userid, lv_bpartner_guid.
DATA : lv_f_apprv_part TYPE BU_PARTNER.
READ TABLE lt_ln_approvers INTO ls_ln_approvers
WITH KEY INITIAL_INDEX = '0000000001'.
IF sy-subrc EQ 0.
MOVE ls_ln_approvers-approval_agent+2(12) TO l_userid.
CALL FUNCTION 'BP_CENTRALPERSON_GET'
EXPORTING
iv_username = l_userid
IMPORTING
ev_bu_partner_guid = lv_bpartner_guid
EXCEPTIONS
no_central_person = 1
no_business_partner = 2
no_id = 3
OTHERS = 4.
IF sy-subrc = 0.
CALL FUNCTION 'BUPA_NUMBERS_GET'
EXPORTING
iv_partner_guid = lv_bpartner_guid
IMPORTING
ev_partner = lv_f_apprv_part.
ENDIF.
ENDIF.
We get the BP number of the first Budget Owner 1
Here, we superseed the field l_s_bbp_sc-approver_id
whereby it may be wrong due to Added Approver.
IF l_s_bbp_sc-approver_id IS NOT INITIAL.
IF lv_f_apprv_part IS NOT INITIAL.
IF l_s_bbp_sc-itm_guid IS NOT INITIAL.
CALL FUNCTION 'RH_STRUC_GET'
EXPORTING
act_otype = 'BP'
act_objid = lv_f_apprv_part
act_wegid = 'EBP-UP'
act_begda = sy-datum
act_endda = sy-datum
act_tdepth = 4
TABLES
result_tab = lt_result_tab
EXCEPTIONS
no_plvar_found = 1
no_entry_found = 2
OTHERS = 3
IF sy-subrc = 0.
READ TABLE lt_result_tab INTO ls_result_tab WITH KEY
otype = 'O'.
IF sy-subrc EQ 0.
l_s_bbp_sc-zzapprov_orgunit = ls_result_tab-objid.
ELSE.
ENDIF.
ENDIF.
ENDIF.
Thanks,
RR

Hi Experts,
Any suggestions. Thanks.
Thanks,
RR

Creating a new project with custom fields using web services

I've been trying unsuccessfully for the last week or so to successfully create a new project from web services and I believe the main problem that I've been running into is that one of the required fields is a custom field. I've tried creating the Project
in a couple of different ways and haven't had any success up to this point, so any help would be appreciated. I've tried creating it with both a REST call to /_api/ProjectServer/Projects and a SOAP call to /_vti_bin/PSI/Project.asmx. Below are the best shots
I've made at the two different calls with the errors I received. If anyone has any leads on the best way to do this the help would be appreciated!
REST POST /_api/ProjectServer/Projects
'odata.type' : 'PS.PublishedProject',
'Name' : 'OData Name',
'Custom_9d77d62aa92e4d40adc8446c90eb7456' : "O&M"
Response
error: {
code: "11713, Microsoft.ProjectServer.PJClientCallableException"
message: {
lang: "en-US"
value: "PJClientCallableException: CustomFieldRequiredValueNotProvided CustomFieldRequiredValueNotProvided mdpropuid = 9d77d62a-a92e-4d40-adc8-446c90eb7456"
SOAP POST /_vti_bin/PSI/Project.asmx
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:proj="http://schemas.microsoft.com/office/project/server/webservices/Project/" xmlns:projds="http://schemas.microsoft.com/office/project/server/webservices/ProjectDataSet/">
<soapenv:Header />
<soapenv:Body>
<proj:QueueCreateProject>
<proj:dataset>
<ProjectDataSet xmlns="http://schemas.microsoft.com/office/project/server/webservices/ProjectDataSet/">
<Project>
<PROJ_UID>e1c2d38b-1529-4128-b707-42a94045e55b</PROJ_UID>
<PROJ_NAME>Proj Dept Test 2</PROJ_NAME>
<PROJ_TYPE>0</PROJ_TYPE>
</Project>
<ProjectCustomFields>
<CUSTOM_FIELD_UID>4802a711-62a0-4f84-8e08-c7d22daadb5b</CUSTOM_FIELD_UID>
<PROJ_UID>e1c2d38b-1529-4128-b707-42a94045e55b</PROJ_UID>
<MD_PROP_UID>9d77d62a-a92e-4d40-adc8-446c90eb7456</MD_PROP_UID>
<FIELD_TYPE_ENUM>21</FIELD_TYPE_ENUM>
<CODE_VALUE>a47930d6-b89d-4f3a-b4e3-522015fe82a1</CODE_VALUE>
</ProjectCustomFields>
</ProjectDataSet>
</proj:dataset>
<proj:validateOnly>true</proj:validateOnly>
</proj:QueueCreateProject>
</soapenv:Body>
</soapenv:Envelope>
Response
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Body>
<s:Fault>
<faultcode>s:Server</faultcode>
<faultstring xml:lang="en-US">ProjectServerError(s) LastError=GeneralUnhandledException Instructions: Pass this into PSClientError constructor to access all error information</faultstring>
<detail>
<errinfo>
<general>
<class name="General Unhandled Exception in _Project.QueueCreateProject_">
<error id="42" name="GeneralUnhandledException" uid="184feeaf-906a-e411-9b2a-00155d388b02" Exception="System.Data.StrongTypingException: The value for column 'PROJ_TYPE' in table 'Project' is DBNull. ---> System.InvalidCastException: Specified cast is not valid.
at Microsoft.Office.Project.Server.Schema.ProjectDataSet.ProjectRow.get_PROJ_TYPE()
--- End of inner exception stack trace ---
at Microsoft.Office.Project.Server.Schema.ProjectDataSet.ProjectRow.get_PROJ_TYPE()
at Microsoft.Office.Project.Server.BusinessLayer.Project.FixupProjectType(ProjectDataSet projDS)
at Microsoft.Office.Project.Server.BusinessLayer.Project.QueueCreateProject(Guid jobUid, ProjectDataSet dataset, Boolean validateOnly)
at Microsoft.Office.Project.Server.Wcf.Implementation.ProjectImpl.<>c__DisplayClasse.<QueueCreateProject>b__d()
at Microsoft.Office.Project.Server.Wcf.Implementation.WcfMethodInvocation.InvokeBusinessObjectMethod(String businessObjectName, String methodName, IEnumerable`1 actions)"/>
</class>
</general>
</errinfo>
</detail>
</s:Fault>
</s:Body>
</s:Envelope>

Julie,
You can create the fields that are project specifc & you can create fields that apply to all projects but have specific options for projects. Your goal is to create fields that are specific to each project, but right now you get all fields from you old project - is this correct?
From your description below it appears that the fields in your original project are marked as applied to all projects & hence when you create a new project they are inherited. If you mark those fields as applied to certain project & then create a new project those fields will not be inherited.
But you are right in the sense that it is limiting that there is no multi-select for "applies to" field.

Custom field not getting populated in the "Show Results where" drop down

Hi all,
In appointment detail page by clicking on Add button on the user related information section , it takes us to a search layout showing the list of available users.
Here we have to filter the user's based on a custom field which has already been created in the user object. But I am not able to add the custom field in the "Show results where" drop down for which the search has to be done.
It is getting reflected in the normal search layouts.So Can any one tell me why the change is not getting reflected in the user related info search layout?

I tested your use case and you are correct. I would recommend that you submit a service request to CRM On Demand customer care in reference to this issue.

Importing into Address Book with Custom Fields from a Text File.

Hello
I'm a teacher and like to create contacts for my students. The information that I want in each contact besides their name, email address and phone number are their
student id's, semester enrolled, class number and class title. For these four fields I create a "Custom" field with the appropriate names: "ID", "Term", "Course" and "Class" respectively.
All this information I can download from the school's server in a CSV file.
To import the information into Address Book, I choose "File -> Import -> Text File" and then select the CSV file that I downloaded. The import utility opens up correctly showing all the fields I would like to import, however, many of the fields are marked as "Do not import." When I click on that term to select my Custom fields, they do not show up. Is this a bug or "feature" of the Address Book? It seems to me that if you are allowed to create useful custom fields, you should be able to import data into them as well.
If I'm just ignorant of how to do this, I would appreciate some help. If there is no way to currently do this efficiently, it would be nice to have this feature added to the Address book in the near future.
Thanks for your consideration,
Gary

Thanks for posting your question and the reply from rojok...
I'm a teacher as well - in Entourage I was able to just copy a column of email addresses (say from an Excel spreadsheet, downloaded from the school's server here at U MD) and then create a group and simply paste that list into the group. Address Book makes you do the extra step of importing all the addresses first. (Note: Your last imported list of contacts in this manner shows up as "Last Import" in the groups lists column to the left in Address Book - so to add contacts to a Group there, you select that Last Import group, click once in that list column one contact, say, then select all of the list - then Command + A, for select all - then drag them all to your group you've made - i.e. "MySpringClassList"). This is NOT very intuitive I might add and incredibly cumbersome of a process.
To get around the customizable info I needed to import... I just chose options that I don't regularly use for those things I needed to import - i.e. student I.D., these I placed under "ICQ Other" - that way they're imported at least.
Good luck,
Andrew

Error when add a custom field to source 2LIS_12_VCHDR

Hi Experts,
I'm trying add a custom field to source 2LIS_12_VCHDR. The fields are in LIKP table's append. That are
zz fields. I can see the fields in MCLIKP structure, but I can't see these fields in LBWE transacction when I try update the structure MCLIKP. I don't know if this last is important because when I replicate of the source the fields, they are visible in BW.
The problem is when I try activate the transfer structure. I Can add the fields from the data source to the transfer structure but If try activate the source the error is:
"Error when creating transfer structure /BIC/CCBA2LIS_12_VCHDR in source system XXXX"
I'm forgetting some step?
somebody know other way for do it?
thanks for your help.
Manuel.

Hi
May be the datasource is not active, do the following obviously in development
goto LBWE and click on your datasource; system will ask you for a transport request number give it a name. now save the datasource.
replicate and activate your t/r
hope this helps
Regards

Error adding custom field in POWL

Hi all,
I've added a custom field in POWL for SC.
The problem is when I fill this custom field and push the search button an error is displayed:
"Last query refresh failed due to internal errors; contact your admin."
I've seen there is a short dump in st22. SAPSQL_INVALID_FIELDNAME
I've seen that the select statement is being built dynamically (include LBBP_PDF80).
Within the conditions of the where clause is adding a line with the correct value but is adding another senseless line .
In the custom fields range is always adding a line like this; LOW = space OPTION = CP.
I don't know why. The problem is in the form GETLIST_CUF_ADD_LINE.
If I delete this second condition in debug mode is working fine.
I've tried to find some OSS note but I couldn't find any...
This are the steps I've followed to add the custom field in POWL:
- Add the field to structure /SAPSRM/S_SEARCHFIELDS. (with the same name that it have in st. INCL_EEW_PD_HEADER_CSF_SC )
- Add the field in view /SAPSRM/V_SRC_CR.
- Add the field in DB criteria in the transaction /SAPSRM/POWL_CUST.
- Use the report POWL_D01 for refresh the query.
Do you know what can be the problem?
Thanks in advance.

Which version of SRM are you using ?
Pls. check the attached note, which describes the similar problem :
[Note 1555113 - Dump occurs when searching for customer fields|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1555113]

Customer Field in Standard BI Content

Hi Experts,
in CRM 7.0 there is a feature called Online Reporting which is using the Netweaver BI functionality to directly execute BW reports within CRM. I have set this up and it is working fine for the standard CRM BI content (which seems to be based on BW version 3.x) that is delivered. So I can execute a standard query and the data is then pulled via Query, InfoCube and DataSource synchronously and displayed in the CRM Web UI.
I am now trying to add a customer field to the whole chain so my first task is to enhance the standard extractor. I manged to do this via an append include and BAdI RSU5_SAPI_BADI. When testing the extractor the data for the new field is populated correctly. When checking the data source in RSA1 I can also see the new field in the fields list of the datasource. The fields is also available in the transfer structure. I now mapped an Infoobject (which I had created before) to this customer field of the transfer structure. And then I created a transfer rule to map the field to the communication structure.
In order to test these changes I have created a start routine and set a break-point to see if the data is provided properly. The debugger stops and all the data is there EXCEPT for my new field. Does anybody have an idea what might be missing in my configuration?
Thanks for your help. Points will be rewarded!
Cheers,
Jens

Hi Experts,
unfortunately, I just realized that for CRM 7.0 it is not recommended by SAP in general to enhance the BI content for Online Reporting. As from EhP1 there seems to be an Interactive Reporting Enhancement Workbench to support this requirement. See post from Sven Kriebel:
CRM 7.0 - Enhancement of Data Sources for interactive Reporting
So until the next upgrade I will have to stick with what AET provides.
Anyway, thanks a lot for your helpful answers!
Cheers,
Jens

Custom field - Next/Last Appointment?

Similar Messages

Maybe you are looking for