How to create substituion for COPA value fields?

Hi,
In OBBH i cannot find a destination field for copa value fields. The destination fields are always from SAP standard tables like BKPF and so on.
In this case how can i create a substitution to assign values to COPA value fields?

Hi,
I can see only the following entries in my OBBH user exit, so what is difference between COPA0002 and these :-
SCO10
SGJF1
SGJA1
SGJA2
SGJA3

Similar Messages

How to create code for an additional field in an info set

Hello,
I have an info set in tra SQ02 and the area is HCM with version ERP2004.
I need to create an additional field to show "Work permit" in ad hoc queries. I know that the infotype 0016 has a standard field P0016-ARBER which contains a date if that person has a work permit. System should select the latest record or the one which is valid during reporting period.
The requirement for this new field is that it should just has X if the field P0016-ARBER contains a date (i.e. that person has a work permit). If the field P0016-ARBER is empty, then the new field "Work permit" is also empty. So, the date itself is not enough.
I am not an abaper. I have tried to create a code for my field but there is always problems with the code. I have tried without the line<i>into</i> but checker says I need to. I have tried different places for statement ENDSELECT but without success. How should I do this?
What I have so far is (TYOLUPA = Work permit) is shown below:
select SINGLE ARBER
into TYOLUPA
from PA0016
where pernr = P0016-pernr
and ENDDA = '31129999'.
clear TYOLUPA.
if ARBER ne ''.
then TYOLUPA = 'X'.
endif.
Thanks for your advice!
Regards,
Pipsa

pia,
In extras tab create column "workpermit" in infoset and add that column to Field groups.
Then under record processing event...
DATA : TYOLUPA like PA0016-ARBER.
Under Record processing event.
select SINGLE ARBER
into TYOLUPA
from PA0016
where pernr = P0016-pernr
and ENDDA = '31129999'.
if TYOLUPA ne ' '.
WORKPERMIT = 'X'.
endif.
Don't forget to reward if useful...

Copa there is a option for reset value field / quantity value filed

Hi
As per the sap standard in copa there is a option for reset value field / quantity value filed. We
use this function to reset a quantity or value field depending on the
billing type (For eg L2 (Debit Memo) G2(Credit Memo). This means that
the condition value set in the field is replaced by value 0. Due to
this quantity value filed in copa reflects nil. My client requirement is when profit center document is generated System should display the quantity as nil.
i have tried some enhancement but these enhancement is only used in case of PGI . But in the case of debit and credit memo their is no PGI. first we create debit not request (va01) then billing(vf01) then document is generated .
Can we do the same thing in profit center Accounting? When PCA document
is generated System should display the quantity as nil.
Please let me know some user exit or substitution or Bte we can use ?
Anjali

hi Jerry,
Very appreciated the link you sent. In this article of this link, it gives an example of a conversion from an external to an internal format:
1. '1234 ' -> '00001234'
2. 'ABCD ' -> 'ABCD '
Just wonder why the external format '1234 ' has to be converted to '00001234', what's the purpose of doing this converstion?
Thanks!

How does APEX check for null values in Text Fields on the forms?

Hello all,
How does APEX check for null values in Text Fields on the forms? This might sound trivial but I have a problem with a PL/SQL Validation that I have written.
I have one select list (P108_CLUSTER_ID) and one Text field (P108_PRIVATE_IP). I made P108_CLUSTER_ID to return null value when nothing is selected and assumed P108_PRIVATE_IP to return null value too when nothign is entered in the text field.
All that I need is to validate if P108_PRIVATE_IP is entered when a P108_CLUSTER_ID is selected. i.e it is mandatory to enter Private IP when a cluster is seelcted and following is my Pl/SQL code
Declare
v_valid boolean;
Begin
IF :P108_CLUSTER_ID is NULL and :P108_PRIVATE_IP is NULL THEN
v_valid := TRUE;
ELSIF :P108_CLUSTER_ID is NOT NULL and :P108_PRIVATE_IP is NOT NULL THEN
v_valid := TRUE;
ELSIF :P108_CLUSTER_ID is NOT NULL and :P108_PRIVATE_IP is NULL THEN
v_valid := FALSE;
ELSIF :P108_CLUSTER_ID is NULL and :P108_PRIVATE_IP is NOT NULL THEN
v_valid := FALSE;
END IF;
return v_valid;
END;
My problem is it is returning FALSE for all the cases.It works fine in SQL Command though..When I tried to Debug and use Firebug, I found that Text fields are not stored a null by default but as empty strings "" . Now I tried modifying my PL/SQL to check Private_IP against an empty string. But doesn't help. Can someone please tell me how I need to proceed.
Thanks

See SQL report for LIKE SEARCH I have just explained how Select list return value works..
Cheers,
Hari

How to create wizard for a custom mainenance view/view cluster

Hi Experts,
I have created 5 custom maintenance view and have maintained all the views sequencially and have made the first mainenance view as the start view & header entry and all other views are child or subview of the header view in a custom view cluster. But I want a wizard to help the user / end user successfully enter all the required values for all child views, it will help the user to navigate from the start view to all the child views where the fields of the wizard will be associated to the child maintenance views.
Please suggest how to create wizard for view cluster.
I'll give max reward point for the helpful answer.
Thanks in advance
koustav

Hello Pasapula
When you are in the View Cluster maintenance dialog (SE54) click on dialog "Events".
Below the field for the view cluster you have an additional field <b>FORM routines main program</b>. There you have to add the main program containing the FORM routines called by the VC events.
For example: I had defined a normal report containing an include with all the FORM routines. The report contains only the following lines of coding:
report zus_0120_u1.
* Common Data und access routines for user exits in VC maintenance
include LSVCMCOD.
include zus_0120_f1. "FORM routines for VC events
Now in the "Events" dialog of the view cluster maintenance you assign your FORM routines to the events.
Regards
Uwe

How to create F4 for the standard transaction

Hi all ,
How to create F4 for the standard transaction for a particular field .
Bye

Santosh,
You can create F4 values for a field in a standard Transaction .
1. First search for a standard search help meeting your requirement .
2. If you don't find one, create your own custom (z) serach help .
( 1 is preferable )
After that, include that serch help to the standard field in the transaction .
For this u need to go to the screen
( F1->F9-> screen-> Field )
Click on the property of the field and include the search help .
You ll require the access key from the basisi guys as u r changing standard .
Hope it helps,
~ laxmi
Reward for helpful answers

How to create variant for table/view ?

Hi,
When I go through SM30, I find a radio button called variant. I don't know the effect.
Can anyone tell me how to create variant for table / view ?
I want to know when we need to create variant for table/view.
Best regards,
Chris Gu

hi ,
Whenever you start a program in which selection screens are defined, the system displays a set of input fields for database-specific and program-specific selections. To select a certain set of data, you enter an appropriate range of values.
For further information about selection screens, refer to Selection Screens in the ABAP User's Guide.
If you often run the same program with the same set of selections (for example, to create a monthly statistical report), you can save the values in a selection set called a variant
Procedure
To create a new variant:
       1.      On the ABAP Editor initial screen, enter the name of the program for which you want to create a variant, select Variants, and choose Change.
       2.      On the variant maintenance initial screen, enter the name of the variant to be created.
Note the naming convention for variants (see below).
       3.      Choose Create.
If the program has more than one selection screen, a dialog box for screen assignment appears. The dialog box does not appear if the program only has one selection screen. The selection screen appears in this case.
       4.      If there is more than one selection screen, select the screens for which you want to create the variant
5.      Choose Continue.
The (first) selection screen for the report appears.
If your program has more than one selection screen, use the scroll buttons in the left-hand corner of the application toolbar to navigate between them and to fill the fields with values. If you keep scrolling forwards, the Continue button appears on the last selection screen.
       6.      Enter the desired selection values, including multiple selection and dynamic selection.
       7.      Choose Continue.

New COPA Value field not populating in BW

We created a NEW value field (VV0056) in SAP COPA that is NOT pulling manual journal entries into BW (document types AB and SA). All other value fields are pulling in all document types and balance to SAP u2013 itu2019s this new one that is not. We do not have any restrictions on selection of data coming into BW.
The manual journal entry is in our CE1* table in R/3.
We are still 3.x data loading in our BW 7 system.
Any ideas on what to look for? Your input is greatly appreciated.
Renee Mercede

Hi Renee
The new fields that has been added must be either in the COPA table or the corresponding datasource.
If it is added in the table
1) You need to enhance the corresponding datasource with a z-field that wiill represent the field added in the table.
2) This field will have to be populated through an ABAP routine.
3) Check the populated field values in RSA3.
4) Replicate the datasource in BW.
5) Create infoobject for the enhanced field.
6) Add infoobject in the corresponding BW data targets.
7) Change transformations / UR's - TR's.
8) Extract data.
If it is added in the datasource - which means you know from which base table this field needs to be populated.
Carry out steps (2) to (8) from above.
Cheers
Umesh

COPA Value Fields maximum limit

Hi,
I read that there is a limit on the number of value fields that you can have in an Operating Concern, which is 120. There is an OSS Note (160892) that describes how you can extend this number to more than 120, however SAP puts a disclaimer that it is not responsible for any problems that result from implementing the note.
Has anyone used this note to extend the value field limit? Alternatively, does anyone know of any other method of creating more than 120 value fields in an Operating Concern?
Thanks

Hi,
I have also faced same situation earlier. Luckily, at that time, the Client agreed to abide by the SAP's suggestion. I think that it is not advisable to pooh pooh the SAP's advice. Kindly shows this OSS note to your employer and put the responsibility on them if something goes wrong. Then you can take up the adventure.I think that nobody on earth can go against the advice of SAP.
Cheers, Thanks.

Delete COPA value fields in a productive system

Does anyone have practical experience with deleting COPA value fields in a productive system?
The issue is that old, no longer used value fields should be deleted from a productive system to allow creating new ones, as the maximun number of value fields is reached.
An alternative would be to delete the prior transaction data captured on these no longer to be used value fields and rename them for their new use (to avoid that different kind of old and new data is reported on the same value field).
I am refering to the documentation on transaction KEA0 (or OSS note 160892 up to release 4.5), where it is mentioned that deleting value fields should only be done for operating concerns that have not yet been used productively. Did anyone do this already in a productive system?
Cheers, Peter

To delete characteristics or value fields, you should perform the following
activities:
1. Delete the corresponding characteristics and value fields from
Customizing in all clients (this includes forms, reports, planning
layouts, and so forth). To locate characteristics and value fields, use
the appropriate where-used list in the Customizing Monitor. You can
access it by choosing Tools -> Analysis -> Check Customizing Settings
(TA KECM).
You can jump directly from the where-used list to the relevant
Customizing transaction and then delete the appropriate field there.
2. Switch to the screen for maintaining the data structure of an
operating concern (Maintain operating concern).
3. If you need to effect other changes to the datastucture for the
operating concern before making any deletions, effect those changes and
save the data structure.
4. In order to be able to select the fields of the data structure,
choose Extras -> Characteristics (or Value fields) -> Unlock.
5. Select the characteristics and value fields to be deleted and remove
them from the data structure with the "Reset fields" function.
6. Reactivate the operating concern. The system starts by checking
whether the operating concern contains any data and whether the fields
to be deleted are still being used in any Customizing settings.
7. If none of the fields are still in use, the system then starts the
re-activation. If the operating concern does not contain any data or
does not require the database system to be converted, the tables are
activated. You are then able to activate the environment for the
operating concern. In this case, the following activities no longer
apply.
If the operating concern already contains data, a system message tells
you that the database needs to be converted. If you proceed, an
activation log appears (at the top of the list).
8. Analyze the activation log. If it only contains error messages
telling you to convert the tables, proceed with the next activity.
You must otherwise remove the cause of the errors before the tables can
be converted. In this case, you should answer "No" to the next prompt,
which asks whether the conversion transaction should start.
9. If you still only receive error messages telling you to convert the
tables, choose "Back" and start the conversion.
10. Plan a job for the conversion. A list of the tables to be converted
is shown for this. If the tables only contain a small amount of data
(less than 10 000 records), then all the tables can be converted in one
job. In that case, you can select all the tables.
For larger tables, conversion should take place in several jobs.
However, you should ensure that table CE4xxxx (where xxxx = operating
concern) is the last table to be converted.
Warning. No other changes can be made to the operating concern during
the conversion.
A copy of the table is generated during the conversion. The database
system should have sufficient memory available for this copy.
To schedule conversion as a job, use the "Schedule selections" function.
You can display the current status of the conversion by selecting the
"Refresh" icon. Tables disappear from the list once they have been
converted sucessfully. If a conversion is taking a while, it is also
possible to leave the transaction. You can then continue the conversion
using DB requests -> Mass processing in one of the following ways:
With the job overview. You access this by choosing System -> Services ->
Jobs.
Using the database utility transaction. You access this by choosing
Utilities -> Database Utility in the ABAP Dictionary menu.
You can use the status function to call up the status of the operating
concern during operating concern maintenance. You need to activate all
tables after conversion.
11. To analyze errors that have occurred during the conversion, you can
use the database utility transaction by choosing Extras -> Logs. The log
has the same name as the conversion job: TBATG-date. You can also
restart the conversion with this transaction.
For more information on the database utility, choose Help -> Application
help while still in the above transaction.
12. Once you have activated all the tables in the operating concern,
generate the operating concern environment from within operating concern
maintenance.
You can then use the operating concern again.
Please, refer to the IMG documentation under Controlling ->
Profitability Analysis -> Structures -> Define operating concern
-> Maintain operating concern, for further details.
Hope it helps

COPA value field not getting complete SD condition value

Hi Gurus,
I find a strange issue when a billing document is transferred to COPA (well basically, after a billing document is released to accounting, all the controlling docs and COPA docs are generated). The issue is, I have a SD pricing condition which has been assigned to COPA value field. I also have the transfer +/- sign checked on this value field. Now consider the following 2 scenarios:
Scenario 1: In VKOA, two different G/l accounts have been assigned to the corresponding pricing condition account key. These 2 G/L accounts have been defined as cost elements with category '12' (its related to sales deduct). and fall under the same cost element group. When a billing doc is posted to accounting and hence to COPA, I see that there is no value in the value field and the corresponding condition type. Then I ran a simulation using KE4ST and found that I have two lines with the same pricing condition type and value field but one carries a positive value and the other one carries a negative value. Then I came to a conclusion that may be these two lines are netting out and hence there is no value being posted on the value field.
Scenario 2: In VKOA, I have assigned two different G/L accounts which fall under different cost element group and one is defined as category 12 and the other as category 1. This time I see that only 1 line of value field is brought into COPA corresponding to the pricing condition and hence I see a value in COPA value field. But business doesn't want to go with scenario 2 as they don't want to use two cost elements in different cost element group. Also one is sales deduct and the other is primary cost/ cost reducing revenue. So there is a balance getting accumulated in the primary cost/cost reducing revenue element.
How do I resolve this issue to post a value to the COPA value field using scenario 1? I have also tried to uncheck the transfer +/- sign but I am unable to even release a billing doc to accounting as it is giving me a error message,: "correct the value field assignment for the condition type".
Please help me !!
Regards,
Sony

Version of SAP?

How to create Criterian For more than one table

Hi,
I have one problem how to create criteria for more than one table in that using one criteria hot to get the values from database in that more than onetable for getting these values .Please send me the exampke code.
reagrds,
raghu

Hi,
I don't think its possible to create fieldcatalog for different tables,
but if you want to do so create a dummy table which has all the fields which you want in fieldcatalog.
populate the data from different table to that dummy table
then create fieldcatalog for that table and pass it in the function module...
Regards,
Siddarth

SD- conditions to be mapped to COPA value field data in BI

Hi Experts,
I have a req where in I have to map condition level Sales order data to some COPA value fields. Currently for one Sale order item there are multiple conditions that means multiple line items. But when I try to find the COPA value field for the same same (Sales order, Sales order item ) key I get only one line item.
This has to be done for BI integration, but needs to be done at the source system level.
So my questions are,
1) How can we get the condition level data from COPA? Is it possible to fetch the data at that granularity?
2) Is it possible to integrate SD & COPA data on condition level i.e. at Sales order, sales order item & condition level.

Hi,
In KEA0, Data structure tab click on pencil button (change view).
Then click on -> change
Now you will be able to select new value fields
Rememeber, after changing click on save, activate and then back button. system will ask for regeneration, click ok.
Regards
Raghu

What is authorization object and how to create it for a table

Hi All,
What is authorization object and how to create it for a table?
Thanks

Hi
Authorization
For authorization checks, there are many ways of linking authorization objects with user actions in an SAP system. The following discusses three possibilities in the context of ABAP programming.
Authorization Check for Transactions
You can directly link authorization objects with transaction codes. You can enter values for the fields of an authorization object in the transaction maintenance. Before the transaction is executed, the system compares these values with the values in the user master record and only starts the transaction if the appropriate authorization exists.
Authorization Check for ABAP Programs
For ABAP programs, the two objects S_DEVELOP (program development and program execution) and S_PROGRAM (program maintenance) exist. They contains a field P_GROUP that is connected with the program attribute authorization group. Thus, you can assign users program-specific authorizations for individual ABAP programs.
Authorization Check in ABAP Programs
A more sophisticated, user-programmed authorization check is possible using the Authority-Check statement. It allows you to check the entries in the user master record for specific authorization objects against any other values. Therefore, if a transaction or program is not sufficiently protected or not every user that is authorized to use the program can also execute all the actions, this statement must be used.
AUTHORITY-CHECK OBJECT object
                        ID name1 FIELD f1
                        ID name2 FIELD f2
                        ID namen FIELD fn.
object is the name of an authorization object. With name1, name2 ... , and so on, you must list all fields of the authorization object object. With f1, f2 ... , and so on, you must specify the values that the system is to check against the entries in the relevant authorization of the user master record. The AUTHORITY-CHECK statement searches for the specified object in the user profile and checks the useru2019s authorizations for all values of f1, f2 ... . You can avoid checking a field name1, name2 ... by replacing FIELD f1 FIELD f2 with DUMMY.
After the FIELD addition, you can only specify an elementary field, not a selection table. However, there are function modules available that execute the AUTHORITY-CHECK statement for all values of selection tables. The AUTHORITY-CHECK statement is supported by a statement pattern.
Only if the user has all authorizations, is the return value sy-subrc of the AUTHORITY-CHECK statement set to 0. The most important return values are:
·        0: The user has an authorization for all specified values.
·        4: The user does not have the authorization.
·        8: The number of specified fields is incorrect.
·        12: The specified authorization object does not exist.
A list of all possible return values is available in the ABAP keyword documentation. The content of sy-subrc has to be closely examined to ascertain the result of the authorization check and react accordingly.
REPORT demo_authorithy_check.
PARAMETERS pa_carr LIKE sflight-carrid.
DATA wa_flights LIKE demo_focc.
AT SELECTION-SCREEN.
AUTHORITY-CHECK OBJECT 'S_CARRID'
                  ID 'CARRID' FIELD pa_carr
                  ID 'ACTVT' FIELD '03'.
IF sy-subrc = 4.
    MESSAGE e045(sabapdocu) WITH pa_carr.
ELSEIF sy-subrc <> 0.
    MESSAGE e184(sabapdocu) WITH text-010.
ENDIF.
START-OF-SELECTION.
SELECT carrid connid fldate seatsmax seatsocc
    FROM sflight
    INTO CORRESPONDING FIELDS OF wa_flights
    WHERE carrid = pa_carr.
    WRITE: / wa_flights-carrid,
             wa_flights-connid,
             wa_flights-fldate,
             wa_flights-seatsmax,
             wa_flights-seatsocc.
ENDSELECT.
Regards
Hitesh

How to create program for bapi?

hi all,
how to create program for bapi?
reply me soon now.....
can anybody help me.....
thanks,
S.Suresh.
Title was edited by:
Alvaro Tejada Galindo

Hi ...Here is the step by step procedure for creating BAPIs.
There are 5 different steps in BAPI.
- Create BAPI Structure
- Create BAPI Function Module or API Method.
- Create BAPI object
- Release BAPI Function Module.
- Release BAPI object.
Step1. Creating BAPI Structure:
- Go to <SE11>.
- Select Data Type & Enter a name.
- Click on Create.
- Note: Always BAPI should be in a development class with request number (Not Local Object).
- Select Structure & hit ENTER.
- Enter the fields from your database. Make sure that the first field is the Primary Key Field.
- Then SAVE & ACTIVATE.
Step 2. Creating BAPI module:
- Enter TR.CODE <SE37>.
- Before entering any thing, from the present screen that you are in, select the menu
Goto -> Function Groups -> Create Group.
Enter a name (Note: This name Must start with ZBAPI)
Let this screen be as it is and open another window and there, enter TR.CODE <SE80).
Click on the Third ICON that says Inactive Objects.
Select the group that you just created and click on Activate.
Notice that the group you created will disappear from the list of inactive objects.
- Go back to ><SE37> screen and enter a name and hit <ENTER>. Then enter the group name that you just created and activated.
NOTE: When you release a function module the respective group will be attached to that particular application. It cannot be used for any other application. NEVER include an already existing group that is attached to another module.
Now click on the first Tab that says [ATTRIBUTES] and select the radio button that says remote-enabled module since we will be accessing this from any external system.
Then click on the second tab that says [IMPORT].
Enter a PARAMETER NAME, TYPE and the structure you created in the first step. Also select the check box Pa. All remotely enabled functional modules MUST be Pa enabled, where Pa means Passed by Value and if you dont select Pa, then that means it will be passed by reference..
Then click on tab that says [EXPORT].
Enter the following as is in the first three fields
RETURN TYPE BAPIRETURN (These 3 field values are always same)
Here also select Pa meaning Pass by value.
Note: BAPIRETURN contains structure with message fields.
Then SAVE and ACTIVATE.
Step 3. Creating BAPI object:
- Enter Tr.Code <SWO1> (Note. It is letter O and not Zero).
- Enter a name and then click on create. Enter details.
NOTE: Make sure that that Object Type and Program name are SAME.
- Enter Application M, if you are using standard table Mara. If you are using your own database then select Z at the bottom.
- Then hit <ENTER>.
- Now we have to add Methods. High light METHODS and then select the following from the menu:
Goto Utilities -> API Methods -> Add Methods.
- Enter function Module name and hit <ENTER>.
- Select the second FORWARD ARROW button (>)to go to next step.
- Check if every thing looks ok and again click on FORWARD ARROW button (>).
- Then select YES and click on <SAVE>.
- Now on a different screen goto TR.CODE <SE37>. Enter Function Module name and select from the top menu Function Module -> Release -> Release.
- Goback to TR.CODE <SWO1>.
Here select the menu combination shown below in the same order.
- Edit -> Change Release Status -> Object Type Component -> To Implemented.
- Edit -> Change Release Status -> Object Type Component -> To Released.
- Edit -> Change Release Status -> Object Type -> To Implemented.
- Edit -> Change Release Status -> Object Type -> To Released.
- Then click on <SAVE>.
- Then click on Generate Button (4th button from left hand side looks like spinning wheel).
- Then Click on the button that says PROGRAM to see the source code.
To check if this is present in work flow goto TR.CODE <BAPI>.
Here it shows business object repository.
- First click on the middle button and then select ALL and hit ENTER.
- Goto tab [ALPHABETICAL] and look for the object that you created. This shows that the BAPI object has been created successfully
Overall Info :
http://help.sap.com/saphelp_47x200/helpdata/EN/00/32a43697bc11d1acf9080009b0fb56/frameset.htm
BAPI Creation Info :
http://help.sap.com/saphelp_47x200/helpdata/EN/e0/9eb2370f9cbe68e10000009b38f8cf/frameset.htm
Reference :
http://help.sap.com/saphelp_47x200/helpdata/EN/00/32a43697bc11d1acf9080009b0fb56/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/EN/00/32a43697bc11d1acf9080009b0fb56/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/EN/e0/9eb2370f9cbe68e10000009b38f8cf/frameset.htm

How to create substituion for COPA value fields?

Similar Messages

Maybe you are looking for