OBXR- Special GL Transaction Types - Modify Fields

Hello Gurus. We are on ECC 6.0 with New GL. Is there a way to modify which fields are available for the Special GL Transaction types in OBXR ? For example: In OBXR go to Properties. We selected Down Payment/Down payment request, later on when we enter a document via FB01 or FB50 or when we post a payment via F-28, and we select Posting Key 09 or 19 and use the Special GL Indicator we are able to display and enter information in BSEG-PRCTR (Profit Center field).
If on the other hand in OBXR we set up another Special GL Transaction type and we select Others, then BSEG-PRCTR (profit center field) is not even available, but we are able to enter BSEG-ZFBDT and later on modify this same field (BSEG-ZFBDT) via FB02.
I would greatly appreciate your guidance in how to modify/include additional fields in these Special GL Transaction types. Thanks!

Hi Enrique,
Are you referring to the document screen layout when you enter the document in the special GL transactions?
This is controlled by the field status of the posting key in question. Using transaction code OB41you can double click on the posting key (say 09) and inside you find something called as maintain field status. Clicking on the same, you will be able to see various groups under which you can make the necessary settings like optional/reqd/suppressed.
Thanks
Aravind

Similar Messages

LSMW for Special GL transaction

Hi,
I am doing a LSMW for upload open items for special GL transaction (TYPE W) with a Batch input. I couldn't do with the standard method (RFBIBL00) because the dynpro for SGL type W is very different. The problem is that the posting is not passing to the second position. It reads all the information but in the step 'convert data' only reads the first posittion (the one of the SGL). In the steps 'FIeld Mapping and conversiont' I can only assing the information of the SGL's dynpro.
Any idea?
Thanks,
Cecilia

For sugestion, define 'W' as default value in your recording and remove this field from upload sheet. If you got more than one entries like that execute in separated sheets.
If the situation remains contact a SAP or presence support to analyse your system.
Good luck and best regards

Transaction Type

Hi Experts,
Is is possible to default a transaction type XXX (Field: COBL-RMVCT) for a GL Account when the user using transaction codes F.13( auto clearing) and F-03 (clearing GL account).
Thanks in advance
laxmi.

Hi
We can do that by using substitutions at transaction GGB1.
Thanks
Sandy

Modify Transaction Type - field BEWAR

Can "Transaction Type" field BEWAR be updated in posted documents? Field BSEG-BEWAR is not an allowable field for change in OB32.
We have created a new transaction type and would like to update many documents with this new Transaction type for reporting purposes. Is there a way other than OB32 to select a field as changable?
Thanks

Hi Jeff,
the transcation type is normally used in the consolidation ledger, and balances are kept per transaction type. Any field which is also used in other ledgers cannot be modified in G/L documents only. It always means 'reverse in G/L and post with new value'.
Ingrid

Transaction type field not copied into FLAGLFLEXT or FLAGLFLEXA

Dear all,
I would like to run a query on the transaction types used for posting line items. (initial balance, changes on the account, ending balance). However if I look into the totals table (new GL: FLAGLFLEXT or FLAGLFLEXA) I see the field transaction types present, but it has not been filled in.
Can anyone help me with finding a solution for this. Two possiblities:
1. How to get the transaction type into the totals table. The field is present, why is it not filled? Customizing?
2. How can I build a simple query from another table to see the transaction types used
Thanks!

The transaction type is there in BKPF, which you can use to link to FAGLFELXA. The common key is BUKRSBELNRGJAHR.

Transaction Type field not getting value in F-05 transaction

Hi All,
When ever we are doing a reverse posting for foreign currency valuation using F.05 Tcode it will create a BDC session where we can execute this batch Input session thru SM37.
This will use F-05 Tcode to post the the entries, but the problem is one of the field Transaction Type is not getting value for some of the GL account numbers range. This is totally SAP standard program take cares of it. Transaction type field value shuld be populated by '990' value for this GL account range, this is fixed. So is thr any User exit or Screen exit for this Tcode or how we can populate the value....
Help me...
Chandar
Edited by: Bala Chandar on Feb 12, 2009 1:25 PM
Edited by: Bala Chandar on Feb 12, 2009 1:28 PM
Edited by: Bala Chandar on Feb 12, 2009 1:33 PM

Hi Mr/Mrs Bala Chander,
I am having the same problem.
When running F.05 a BIM is created for GL account X. GL account X has a field status in which transaction type is defined as a required field because of BCS / ECCS. We have a substitution rule in place which should default the transaction type, based on several criteria. But when executing the BIM, I see that nothing is filled in field transaction type. Did you find a proper solution for your problem? Changing the field status is not an option in my opinion.
Regards,
Joep

Payment Terms field in F-43 Transaction(for Vendor special GL transactions)

Hi experts
Our Client requirement is like this:
Our Client uses F-43 for entering the special GL Transactions (I am sure that SAP has given F-48 but this is the way they use for quiet long time).
So here they enter Posting Key 39 and Special GL Transaction "J" which they have customised for some purpose. In this line item they want to see Payment Terms also. But SAP has not given that field in the transaction F-43 with Special GL functionality.
Even if we try in F-48 also this field is not given by SAP.
We have already cheecked by enabling the Payment Terms in Positng Key and GL Field Status group but of no use.
Is there any way we can get this field available for entry in F-48 or F-43 for Special GL Transactions.
Thanks in Advance
Rayala

Hi Rayala，
The functionality you required is not avaliable for down payment. because the BSEG-ZTERM is not necessary for down payment. if there is down payment happened, this down payment should be cleared with vendor invoice immediately.
The Alternative solution: suggest you to consider to use the allternative reconciliation account function instead of using special G/L indicator, then the BSEG-ZTERM could be avaliable for entering.
Hope the above information are useful to you!
With Best Regards,
Gladys Xing

Use of field - Transaction Type in F.01

Dear All,
Can anyone explain the use of field Transaction Type in Dynamic Selection in transaction code F.01.
If I have understood correctly, these are related to fixed assets. If I select any transaction type, say for instance 120, which is related to acquisitions, F.01 should display the related figures.
However, I do not get any display, inspite of having various transactions with transaction type 120.
Can anyone explain me why this is happening?

Hi,
I have gone into transaction f.01 and am unable to find the component Transaction type in dynamic selections. If however you want to find Transacttion type 120 use transaction SE16n and table ANEKPV add in the transaction types (technical name BWASL) add other parameters example company code, period etc to get the related information.
Award points if useful.
Sadie Gajanand

Authorization Control on Transaction Type Fields

Hi Friends,
I have created 4 customised fields in Complaint Transaction Type. Lets say A1,A2 and B1,B2.
Now the requirement is to control the fields based on roles or users. Is this Possible? if yes how?
I mean UserA will be able to see and edit field A1 and A2 of Transaction Complaint where as UserB will be able see and edit field B1 and B2 of same transaction.
Regds...
Arup

Hi Arup,
You have to create two seperate configs. Based on the Business Role of the logged in user you can swap the same in method
DO_CONFIG_DETERMINATION.
Regards,
Masood Imrani S.

Controling field display by Transaction Type

Hello,
Is it possible to control field display by Transaction Type in CRM 7.0 anymore given that we have the Web UI now. I remember from my 5.0 experience that we used CRMV_SSC to control this at transaction type. I would imagine, the functionality has not been taken away but rather changed to a different place where we control this. Anybody dealt with a similar requirement? Any ideas / suggestions/ tips?
Essentially for transaction ZOR1 we want to surpress a tab / fields, but for ZOR2 we want to keep those available. ZOR1 and ZOR2 belong to the same transaction category.
Thanks in advance..
KK

Kevin,
This is all controlled now by Configurations in the WebUI, along with the Component/view. As an example, via the WebUI try going into each of the transaction types. You have not said what kind of transaction types you were referring to, so I'm just going to assume it's Opportunities for the time-being. So, If you click on each of the transaction types and when the screen is displayed place the cursor on an editable field and press F2. This will then display the technical details behind the screen. Here you'll see that each tranx type has it's component/view name and context node. You will also see the configuration as well. So, the transaction types are actually controlled by the code and screen design behind the component and view, but there can be a different screen layouts for the same tranx type dependning of the configuration used. And, this configuration is normally identified by the business role that you're currently using.
So if that was a bit wordy, but if you look at the technical details behind each of the tranx types it should become clear.
Jason

Change transaction type group for transaction type

Hi
Is it possible to change the transaction type group for a TTY.For ex i want to change for 270 and 151 -TTY GRP -32 and 33 respectively.As of now it is TTY grp is 25 and 10.I need to change this so that in Asset history sheet when i do ABT1N i want these values to be in field transfer and not in acquisition and retirement in respective company codes.
Where is TTY grp are set for TTY.Can it be modified.Please suggest.

For creating transaction type see the wiki.
In the transaction types you assign them!
For 151
SPRO:
Financial Accounting / Asset Accounting / Transactions / Acquisitions / Define Transaction Types for Acquisitions.
Assign there the asst hist group you need for this transaction type
For 270
SPRO:
Financial Accounting / Asset Accounting / Transactions / Retirements / Define Transaction Types for Retirements
Assign there the asst hist group you need for this transaction type

CIN Transaction Type Concept and Linkage

Hi all !
Can anybody Please explain the transaction type Concept in CIN. ( Like GRPO) and its linkage with the excise transactions processing.
Also i need the customization settings for Transaction Type and its linkage with Accounting.
Thanks in Advance !!!!!

Few more inputs on CIN:
See also : SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination and -> Formula-Based Excise Determination.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
Condition-Based Excise Determination
When you enter a purchasing document, for example, a purchase order, the R/3 System automatically calculates the applicable excise duties using the condition technique.
Features : The standard system comes with two tax calculation procedures. TAXINN is only supports condition-based excise determination, whereas TAXINJ supports condition-based excise determination and formula-based excise determination. Both tax procedures contain condition types that cover all of the excise duties and sales taxes applicable.
Since the exact rates of excise duty can vary on a large number of factors, such as which vendor you purchase a material from, or which chapter ID the vendor stocks the material under, you create condition records for every sort of excise duty.
When you come to enter a purchasing document, the system applies the excise duty at the rates you have entered in the condition records.
Customizing : Make the settings in Customizing Basic -> India -> for Logistics General, by choosing Taxes on Goods Movements Account -> Excise Duties Using Condition Technique and -> Settings Determination.
These activities include one activity where you define a tax code for condition-based excise determination.
Master Data - Create condition records for all excise duties that apply, and enter the tax code for condition-based excise determination in each.
Day-to-Day Activities - When you enter a purchase order or other purchasing document, enter the tax code for condition-based excise determination in each line item. The system then calculates the excise duties using the condition records you have created.
When the ordered materials arrive, you post the goods receipt and the excise invoice. The system posts the excise duty to the appropriate accounts for deductible input taxes when you enter the excise invoice.
Creating Condition Records for Excise Duty
1. In the command field, enter FV11 and choose .
2. Enter the condition type that you want to create a condition record for and choose .
The Key Combination dialog box appears.
3. Select the combination of objects that you want to create the condition record for. On the dialog box, Control Code means "chapter ID." So, for example, to create a condition record for a tax that applies to a combination of country, plant, and chapter ID, select Country/Plant/Control Code.
4. Choose .
5. Enter data as required. - In the Tax Code field, enter the dummy tax code that you have defined.
6. Save the condition record.
Formula-Based Excise Determination - When you execute a business transaction involving materials that are subject to excise duty, the system automatically calculates the duty for you.
In order for the system to be able to determine which rate of excise duty to apply, you must have maintained all the data on the Excise Rate Maintenance screen, which you can Master Data®access from the SAP Easy Access screen by choosing Indirect Taxes Excise Rate Maintenance.
You maintain the following types of data:
- Plant master data
You assign each of your plants an excise duty indicator. You can use the same indicator for all the plants with the same excise status from a legal point of view, such as all those that are in an exempt zone. See also the information about manufacturers that are only entitled to deduct a certain portion of the duty (see Partial CENVAT Credit).
- Vendor master data
For each of your vendors with the same excise status from a legal perspective, you define an excise duty indicator. You must also specify the vendor type for example, whether the vendor is a manufacturer, a depot, or a first-stage dealer. You must also stipulate if the vendor qualifies as a small-scale industry. For each permutation of plant indicator and vendor indicator, you then create a final excise duty indicator.
- Customer master data
Similarly, you assign the same excise duty indicator to each of your customers that share the same legal excise status.
Again, for each permutation of plant indicator and customer indicator, you then create a final excise duty indicator.
- Material master data
Each material is assigned a chapter ID.
- Excise tax rate
For every chapter ID and final excise duty indicator, you maintain the rate of excise duty.
If your business only qualifies for partial CENVAT credit, you must customize your system accordingly.
Let us consider an example to illustrate how the system determines which rate of excise duty to apply to a material. Assume you are posting a sale of ball bearings to a customer. The system automatically determines the rate of excise duty as follows:
1. Looks up the customer master data to see what status you have assigned the customer.
Let's assume you've assigned the customer status 3.
2. Looks up the plant master data to see what status you have assigned the plant. Similarly, your plant has status 2.
3. The system looks up the table under Excise Indicator for Plant and Customer to see what the final excise duty indicator is for customer status 3 and plant status 2: It is 7.
4. The system determines the chapter ID of the ball bearing for the plant.
Lets assume the chapter ID at plant for the ball bearings is 1000.01.
5. Finally, the system looks up the table under Excise Tax Rate to see what rate of duty applies to chapter ID 1000.01 under
status 7.
Define Tax Code for Purchasing Documents - In this IMG activity, you define a tax code for the purposes of calculating excise duty when you enter purchasing documents. Only carry out this activity if you use condition-based excise
determination.
- Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
- Assign Tax Code to Company Codes
In this IMG activity, assign the tax code for purchasing documents to the company codes where it will be used.
Only carry out this activity if you use condition-based excise determination.
Classify Condition Types - In this IMG activity, you specify which condition types you use for which sort of tax. Note that this only applies to condition types that you use with the new excise determination method. The system uses this information when you create a document from another one. For example, when you enter an incoming excise invoice from a
purchase order, or when you create an outgoing excise invoice from a sales order, the system determines the various excise duties in the excise invoice using the information that you have entered here. In addition, when you create a purchasing document, the system only uses the condition types that you enter here.
- For taxes on purchases, use the condition types contained in the tax procedure.
- For taxes on sales, use the condition types contained in the pricing procedures.
The standard system comes with sample settings for the tax calculation procedures and pricing procedures.
Use these settings as a basis for your own.
IMG > Logistics - General > Tax On Goods Movement > India > Account Determination
Define G/L Accounts for Taxes - In this IMG activity, you specify which G/L accounts you will use to record which taxes.
Requirements - You have set up G/L accounts for each of the processing keys listed below.
- Assign an account to each of the following posting keys. The accounts for VS1, VS2, and VS3 are used as clearing accounts during excise invoice verification.
- VS1 (basic excise duty)
- VS2 (additional excise duty)
- VS3 (special excise duty)
- VS5 (sales tax setoff)
- MWS (central sales tax)
- MW3 (local sales tax)
- ESA (service tax)
- ESE (service tax expense)
Specify Excise Accounts per Excise Transaction - In this IMG activity, you specify which excise accounts (for excise
duty and CENVAT) are to be posted to for the various transaction types. Enter all the accounts that are affected by each transaction type. If you use sub transaction types, enter the accounts for each sub transaction type as well.
Transaction type UTLZ is used for determining accounts only while posting excise JVs and also if the payment of excise duty has to be done fortnightly. The fortnightly CENVAT payment utility picks up the credit side accounts from the transaction types of GRPO, EWPO, and TR6C for determining the CENVAT and PLA accounts. There is no separate transaction type for fortnightly payment.
Example:
- Excise TT DC ind Account name
- GRPO CR CENVAT clearing account
- GRPO CR RG 23 BED account
- GRPO DR CENVAT on hld account
Specify G/L Accounts per Excise Transaction - In this IMG activity, you assign the excise and CENVAT accounts to G/L
accounts. When you come to execute the various transactions, the system determines which G/L accounts to post to by looking at the:
- Excise group
- Company code
- Chart of accounts
Furthermore, if you want separate account determination settings within an excise group, you can also use sub transaction types.
Requirements
You have already:
- Defined the G/L accounts
- Defined the excise groups
- Maintained the transaction accounts
Activities - For each excise group, assign the excise and CENVAT accounts to G/L accounts. For most businesses, one set of accounts will suffice for all transactions.
Note : you need not remit the CENVAT to the excise department immediately, so maintain the credit account for transaction type DLFC as an excise duty interim account. This will be set off when you remit the duty. Config setting needed to be done in order to get the Excise Details Screen in Material Master.
Even though this functionality is available in enterprise version, a small configuration step has to be made in Screen Sequences for Material Master.
Following document helps you to do this configuration.
- Material Master à Logistics General
1. Go to IMG Define Structure of Data Screen for each Configuring the Material master Screen Sequence.
2. Select your screen sequence. Usually it would be 21. Select the same and click on Data Screen in the left frame.
3. Once the data screens are exhibited, select data screen no. 15, ie. SSq. 21and Scrn 15, which is Foreign Trade: Import Data. Select the same and click on Sub screens in the left frame.
4. Go to the last sub screen i.e. 21-15-6 - SAPLMGD1- 0001 and select the same. Click on tab view sub screen and ensure that the sub screen is blank.
5. Now in the last sub screen i.e. no.6 you delete SAPLMGD1 0001 and instead add SAPLJ1I_MATERIAL_MASTER and in the screen no. 2205.
6. Save the setting.
7. Create a Material Master and check whether in Screen Foreign Trade
Import, Excise related sub screen appears.
Thanks,
Kumar Arcot

Transactional persistence-modifier

Hi,
I'd like to define a field of a persistent class as "transactional". This
field is not mapped to a table column, but it must be rolled-back when
transaction aborts.
According to JDO specification, I tryed to use the "persistence-modifier"
attribute of the "field" element in jdo metadata, as follows:
<jdo>
<package name="it.tasso.model">
<class name="Indirizzo" objectid-class="IndirizzoId">
<field name="id" primary-key="true"/>
<field name="transazValue" persistence-modifier="transactional"/>
</class>
</package>
</jdo>
But at runtime, when the persistent object is retrieved from the
datastore, the following error occurs:
Exception in thread "main" kodo.jdbc.meta.MappingInfoNotFoundException: No
mapping information was found for "it.tasso.model.Indirizzo.transazValue".
I't obvious that there's no mapping information, because that field is
just transactional. In fact, kodo documentation says:
persistence-modifier: Specifies how JDO should manage the field. Legal
values are persistent for persistent fields, transactional for fields that
are non-persistent but can be rolled back along with the current
transaction,
If the persistence-modifier attribute is set to NONE, no errors occurs.
Where's my mistake?

Patrick Linskey wrote:
First of all, thank you very much for your help. I'm the guy you met in
Bologna few days ago (the one who speaks really bad english). ;-)
Now it works, but there is a step further.
If a transactional field is modifyed inside a transaction, the state of
the object is dirty.
If a persistent field of a detached object is modifyed, when the object is
attached its state is dirty.
If a transactional field of a detached object is modifyed, when the
object is attached its state is NOT dirty.
This is a sample code;
KodoPersistenceManager kpm =(KodoPersistenceManager)pm;
kpm.currentTransaction().begin();
Extent ext = pm.getExtent(Indirizzo.class,true);
Iterator it = ext.iterator();
Indirizzo ind =null,attachedInd,detachInd;
if(it.hasNext()){
ind = (Indirizzo)it.next();
//this is a transactional field
ind.setTransazValue("Pippo");
if(JDOHelper.isDirty(ind)){
System.out.println("STEP 1: DIRTY");
detachInd = (Indirizzo)kpm.detach(ind);
pm.currentTransaction().commit();
//this is a transactional field
detachInd.setTransazValue("Pluto");
pm.currentTransaction().begin();
attachedInd = (Indirizzo)kpm.attach(detachInd);
if(JDOHelper.isDirty(attachedInd)){
System.out.println("STEP 2: DIRTY");
} else {
System.out.println("STEP 2: CLEAN");
detachInd = (Indirizzo)kpm.detach(attachedInd);
kpm.currentTransaction().commit();
// this is a persistent field
detachInd.setDes("foo");
kpm.currentTransaction().begin();
attachedInd = (Indirizzo)kpm.attach(detachInd);
if(JDOHelper.isDirty(attachedInd)){
System.out.println("STEP 3: DIRTY");
} else {
System.out.println("STEP 3: CLEAN");
kpm.currentTransaction().commit();
This is the result of the code above:
STEP 1: DIRTY
STEP 2: CLEAN
STEP 3: DIRTY
This means that Kodo in able to detect changes for a persistent field of a
detached object, but NOT for a transactional field. Is it right?
What happens if you explicitly mark that the field is not mapped? You
can do this by putting the following in your mapping file:
<field name="transazValue">
<jdbc-field-map type="none"/>
</field>
-Patrick
Claudio Tasso wrote:
Hi,
I'd like to define a field of a persistent class as "transactional". This
field is not mapped to a table column, but it must be rolled-back when
transaction aborts.
According to JDO specification, I tryed to use the "persistence-modifier"
attribute of the "field" element in jdo metadata, as follows:
<jdo>
<package name="it.tasso.model">
<class name="Indirizzo" objectid-class="IndirizzoId">
<field name="id" primary-key="true"/>
<field name="transazValue" persistence-modifier="transactional"/>
</class>
</package>
</jdo>
But at runtime, when the persistent object is retrieved from the
datastore, the following error occurs:
Exception in thread "main" kodo.jdbc.meta.MappingInfoNotFoundException: No
mapping information was found for "it.tasso.model.Indirizzo.transazValue".
I't obvious that there's no mapping information, because that field is
just transactional. In fact, kodo documentation says:
persistence-modifier: Specifies how JDO should manage the field. Legal
values are persistent for persistent fields, transactional for fields that
are non-persistent but can be rolled back along with the current
transaction,
If the persistence-modifier attribute is set to NONE, no errors occurs.
Where's my mistake?

Go-live in EC-CS:update trading partner and transaction type on Balances

Hi collegues,
We are on a go-live this december for EC-CS (consolidation) but never have used trading partner nor consolidation transaction type so there are not GL account balances differenciated by these two items on our FMGLFLEXT database for the operative ledger.
Which is the best option for the data to be collected into our consolidation ledger in EC-CS (ECMCT database) when data transfer for all our consolidation units will be realtime update from FI?
I really don't know if I must correct the balance on FMGLFLEXT throught FI postings or if just adjustments on EC-CS it's the best option. I'm thinking on the posibility of extracting the Financial Statement at any time from F.01 tx...
Is there any transaction on FI to authomatically update at least the trading partner on GL accounts positions/balances?
Thanks in advance!
Regards,
Rushid

Hi David,
In fact there has never existed any entry for trading partners on GL, AR, AP master data. So consequenly, no balance in FAGLFLEXT/ nor documents on BSEG have ever had these fields populated.
My question is: which is the common option for a go live in such situation? Our users will distribute the current GL balances into "sub-balances" (GLAcctTxtypetradpartner) in an excell file but I do not really know what to do with this data:
- direct postings on BSEG cancelling the previous totals,
- rollup into a Special ledger of the new gl,
- rollup into the Preparations for Consolidation Ledger,
- corrections on ECMCT after the periodic extract...
What would choose?
Thanks!

Transaction type ZGC not possible (posting to affiliated company) in ABSO

Hi all,
We have depreciation areas 01, 30, 31, 32 .
dep area 30, 31, 32 inherits the values from 01.
We want to post credit value to dep area 01 after doing the aqusition .
Hence we created a seperate transaction type ZGC ( in aqusitions- Tcode AO73) and limited it to dep areas 01, 30, 31, 32.
Transaction type ZGC is having credit and " do not post to affliated company " radio button is selected.
Now the issue is when we run ABSO to do a credit post in dep area 01 we are getting the below error .
Transaction type ZGC not possible (posting to affiliated company)
Message no. AA390
Diagnosis
For the current document, you specified either implicitly (via the customer/vendor), or explicitly (with a manual entry), that this posting is to an affiliated company. In this case, Asset Accounting requires you to use special transaction types. This enables the system to separately identify such transactions.
Procedure
Check the line items that you have already entered, and the transaction type you entered.
Not sure why it is asking for affliated company .
It will be great if any one help on this why we are getting this issue.

Hi Daya,
Please try to choose Trans.Type 100 in AO73 transaction code and select the radio button Post to affiliated company under Posting type.
Thanks,
Kumar

OBXR- Special GL Transaction Types - Modify Fields

Similar Messages

Maybe you are looking for