Info structures in credit management

Hi Gurus
What are the different inforstructures (apart from S066) that are useful in credit management.
Ravi

Hi Sankar,
S067 -- Open deliveries/billing documents (KM)
Reward points
Regards,
Govind.

Similar Messages

Info Structure Updation

Hello Every one,
I had 2 issues regarding Info-structures:
1. I Have mentioned Sales Employee in my info-structure as a characteristic. But when i press F4 help for the same, the system does not show the list of Sales Employees in the database. I am not able to figure out the reason why.
2. I have created few Info-structures for Flexible Planning. When I am transferring from my info structure to Demand Management, The info structure automatically reduces the quantity transferred for the current month. I am not able to figure out why.
Any help on the above 2 issues would be greatly appreciated.
Sincerely,
Aji

Hi
If there are a few records, go for manual entry.
If the records are huge data,go for writing upload programe.
There is no standard transaction to upload data from excel sheet.
For other question reg. "Update the infostructure directly" . what do you mean this.
For external data entry like form Excel sheet,you can do without any problem.
Regards
YMREDDY

How to determine the week for credit management?

Is there a transaction that will show the week for which credit is determined. For example, when running RVKRED88, it shows the week the order is processed under.

Hi Rocha,
In Credit management S066 and S067 information structures play a vital role in updating the credit values of a customer. This works in tandem with the update group present in the OVA8 settings in case of automatic credit check.
When an order is created S066 information structure and OEIKW field is updated which increases open order value. when order is delivered S067 information structure and OLIKW field is updated which increases open delivery value and decreses S066-OEIKW
When delivery is billed S067-OFAKW value (Open billing)gets increased and S067-OLIKW gets decreased.
Updation is through the information structures S066 and S067.
In the transaction code OMO1 select the information structure and double click it. You will be faced with parameters pop-up.
In this pop-up you have radio buttons day ,week and Month. _Based on the value you choose here you will get day or week or month for the Period split: info structure field present just besides horizon field of dynamic credit check in OVA8 Screen_If you choose week it will be till the end of the week and if you choose Month it will be end of the month. it is how system considers.
For example if we have created an order today i.e. 19/08/2011 and the Period split: info structure in the OVA8 has 1month.
System evaluates dynamic credit check as today's date + one month =19/09/2011which is =30th september,2011.
So while evaluating credit for the order, system will consider all the open orders whose delivery date is on or before 30th september + open deliveries + open bills + A/C receivables.
Edited by: mokirala tilak on Aug 19, 2011 11:00 AM
Edited by: mokirala tilak on Aug 19, 2011 11:23 AM

Credi management

What is the significance of Update group in Credit management?

there are 3 types of updates group in credit management
1) 000012
2) 000015
3) 000018
the above groups will decide when Info structure S066 and S067 are updated
for 000012 info structures are updated when sales order, delivery and billing is created
for 000015 only when delivery and billing are created structres are updated
for 000018 only when sales order and billing is created info structures are updated.

Link between sales order to Credit management

Where can we link between sales order to Credit management?

HI Gopala rao.,
In VOV8 sales document type there is <b>credit limit & Credit group</b> Where we asign the credit mage,ment data to Order
The configuration part of credit managemnt is
CREDIT MANAGEMENT:
A credit limit may be a customers credit limit, which is the permitted limit of value of open items, such as invoices not yet paid, plus the value of open sales orders.
The credit limit is the total combined value of the following documents:
Net value of sales order
Open Sales order: order created, but not delivered
Open deliveries: delivered, but not invoiced
Open billing doc: value of billing doc, which has not yet been forwarded to accounting
Open items: forwarded to accounting, but not settled.
Types of Credit Check
Simple Credit Check
Automatic Credit Check
o Static
o Dynamic
Simple Credit Check:
SPRO- IMG- SD- Basic Functions- Credit Mgmt/ Risk Mgmt- Simple Credit Check- Assign Credit Check to Doc Types.
Based on sales doc types
It will check all the above-mentioned docs & if the credit limit exceeds, the system responds in the way defined by you in the configuration menu.
Cannot differentiate according to customer
3 ways to Control the Simple Credit Check:
A: warning
B: error message: the doc cannot be saved
C: warning message with delivery block: the doc can be saved but is automatically blocked for delivery.
Automatic Credit Check:
This credit mgmt control is maintained by using the automatic credit control functionality. The automatic credit control divides the sales doc types, the delivery doc types, & goods issue into specific credit groups. It also uses the customers risk category as assigned to the CMD of the payer & assigns an outcome proc to the combination of the above 2 objects, i.e. the credit group & customer risk category along with the credit control area. The definition of customers risk category is carried out in the fin accounting module.
A customers risk category is a grouping category that controls the credit check when automatic credit control takes place. Thus one can assign high-risk customers to risk category for e.g. A01, medium risk to B01 and low risk to C01.
Automatic credit check divides customers in to 3 categories:
High-risk customers,
Low risk customers &
Medium risk customers.
A credit check can only occur at 3 places: Credit Group
Sales order: for high risk customers
Delivery: for medium risk customers
Goods Issue: for low risk customers
Credit Control Area (CCA): highest organizational element in credit management. A credit control area is an organizational unit that is comprised of one or more company codes. A company code can have no more than one credit control area. Defined by FI.
Menu Path to create Credit Control Area: OB45: FI people.
SPRO- IMG- Enterprise Stru- Definition- Fin Accounting- Define Credit Control Area
Credit Control Area Description
0001 Credit control area 0001
1000 Credit control area Europe
Menu Path to Assign Company Code to Credit Control Area: OB38: FI people.
SPRO- IMG- Ent Stru- Assignment- Fin Accounting- Assign Comp Code to CCA
It is possible to assign Credit Control Area to a Sales Area. This is more specific assignment than the assignment to Company Code.
Company code Company name City Credit Control Area Over write CCA
Menu Path for Defining Risk Categories: OB01: FI people
SPRO- IMG- Fin Accounting- Account Receivables & Payables- Credit Mgmt- Credit Control Account- Define Risk Categories.
Risk Category CCA Name
001 4500 Low risk
002 4500 Medium risk
003 4500 High risk
Menu Path for defining Credit Groups: OVA6
SPRO- IMG- SD- Basic Function- Credit Mgmt/ Risk Mgmt- Credit Mgmt:
Define Credit Groups: OVA6
Assign Credit Groups to Sales Docs & Delivery Docs
o Credit Limit check for Order Types: OVAK
o Credit Limit check for Delivery Types: OVAD
Define Automatic Credit Control: OVA8
Define Credit Croups: OVA6
One merely creates a credit group for each differentiation in the doc type. You enter the credit groups when you configure the sales doc types for credit management & define the automatic credit check. The following credit groups are contained in the standard R/3 system:
01: credit group for sales order
02: credit group for delivery
03: credit group for goods issue
CG (Credit Group) Doc Credit Group
01 Credit group for sales order
02 Credit group for delivery
03 Credit group for goods issue
Assign Sales Documents & Delivery Documents:
Sales Doc Type Descp Check Credit Credit Group
OR Std Order D 01
Delivery Type Descp Del Credit Group GI Credit Group
LF Delivery 02 03
Define for each sales doc type whether a credit check should be carried out. Enter D if an automatic credit check should be carried out.
Specify a Credit Group
Specify a Credit Group for the Delivery Type for which you want to carry out a credit check
Specify a Goods Issue Credit Group for the Delivery Type for which a credit check is to be carried out for goods issue.
SIMPLE CREDIT CHECK CANNOT BE ASSIGNED TO DOCUMENTS.
Define Automatic Credit Control:
One can now assign settings to the combination of the Credit Control Area, the Customer Risk Category & the Credit Group.
CCA Risk Cat Credit Group Credit Control
4500 001 01 Low risk sales orders
4500 001 02 Low risk deliveries
4500 001 03 Low risk goods issue
4500 002 01 Medium risk sales orders
4500 002 02 Medium risk deliveries
4500 002 03 Medium risk goods issue
4500 003 01 High risk sales orders
4500 003 02 High risk deliveries
4500 003 03 High risk goods issue
Select line item and go to details, you can decide whether to do Static or Dynamic Credit Check. Credit Horizon can also assigned here. Additional function checks can be performed here:
A credit check when the maximum document value is exceeded.
A credit check when changing critical fields.
The risk category assignment occurs in the same place as the customers credit limit, which is the customers credit management screen. That is, the risk category is assigned to the customer by the Finance in transaction code FD32.
The customer credit master record is divided in to 5 views:
Overview Screen: gives an overview of credit settings in relation to the customer, including his credit limit, credit exposure, the %tage of credit limit used, his payment data & his risk category.
Address: view gives the customers address details as they appear in CMD
Central Data: is a view that shows the total credit limit the customer can receive across all credit control areas as well as the maximum limit he can receive in one credit control area.
Status: view shows the customers actual individual details according to particular CCA being investigated. This includes his credit limit, percentage used, credit exposure, risk category, whether he is blocked due to credit or not.
Payment history: view displays the payments made by the customer for a particular credit control area where a comp code is assigned.
Static Credit Check Dynamic Credit Check
Net Doc Value Net Doc Value
Open Order Open Order
Open Delivery Open Delivery
Open Billing Open Billing
Open Item Open Item
Compares the total combined values of the above-mentioned documents to credit limit. Plus credit horizon. Compares the values of the following documents to credit limit + credit horizon.
Credit horizon has an attached time period that states that the system is not to include sales orders in the total of outstanding items created after that specified period i.e. for the purpose of evaluating credit, you want the system to ignore all open orders that are due for delivery after the horizon date. Maintained for low & medium risk customers.
Update Groups
Basically it is a info structure where system stores all the data about credit limit. The credit relevant data is updated in a info structure, where it is accessed & updated. Thus each automatic credit control must be assigned an update group.
Update Group 000012
Update Group 000015: delivery & billing
Update Group 000018: sales order, delivery & billing.
Update group 000012, updates at:
Sales doc: increased order value
Delivery: decreased order value & increased delivery value
Billing: decreased delivery value & increased billing amount
Invoice: decreased billing amount & increased open item value.
Release Blocked Sales Order/ Deliveries:
VKM3: sales order
VKM5: delivery
VKM4: both
One can see the offending document. Note on the right hand side, the Status Field. This shows the check, the doc failed. If this field is empty, the doc did not fail a credit check, even though it may be in the list of SD documents that are required to be released.
To release the doc, one indicates the doc to be released and then clicks on the Release Button. The result is the offending doc entry, highlighted green. One then proceeds to save, after which you are informed the doc number has been released.
Net value with sub total A, in pricing proc, will be the basis for credit limit.
REWARD if helpfull
Thanks & Regards
Narayana
Message was edited by:
manam narayana

Update info structure S066/S067

Dear all,
we create a delivery without reference to an order. This delivery, although without reference, should update/reduce the open amount in the info structure. We know the order number at time of delivery creation in an own Z-field.
Is someone knowing an user-exit, BadI or customer exit or any other solution to solve this problem?
I will not explain here why we create this delivery without reference but it make sense in this business case.
Thanks.
Kind regards
Frank

Hi Frank,
Check SAP Note 400311 - RVKRED77: Reorganization credit data, new documentation. But before to run the report RVKRED77 check the settings for your credit managament (for this type of delivery), so, check these other notes
SAP Note 425523 - Collection of consulting notes: Credit update
SAP Note 425483 - Consulting note collection: Credit checks
SAP Note 18613 - Checklist for Credit Management
I hope this helps you
Regards
Eduardo

Open Delivery value update error in credit management

Hi
We have credit management active at delivery level. The value of open deliveries is not getting updated correctly for items with material substitution (material determination). For all other items, its getting updated correctly.
E.g Let say the credit limit set in FD32 is 10000 and the credit limit used % is 98 and the credit exposure value is 9800.
Now when I create an order with qty 10 for mat A, it creates a sub item B due to material determination and the value of the item is Rs.1200. In our system, the sub item with TAPS item category is relevant for pricing.
Then I create a delivery in VL01N and save it.
Now if i check in FD33, the credit limit used should be 101% and the credit exposure value should be 11000, but its not updating the open delivery value correctly. Its not considering the value of the new delivery.
However, If I add a normal item (TAN) in the same sales order and create a delivery for that item and save it, its updating the credit exposure based on the value of the normal item in the delivery correctly.
How to make the system update the open delivery values correctly by taking the items with material determination also into account.??
Please advise if any specific settings need to be done.
Regards
Madhu

Hi,
the system updates open values for credit management. These are:
Open sales order credit value (S066-OEIKW)
Open delivery credit value (S067-OLIKW)
Open billing document credit value (S067-OFAKW)
The system updates the open values in standard SIS structures S066 and S067. Technically, the structures are transparent tables. You can display the contents using transaction SE16 or using table maintenance.
The S067-OLIKW will give the open delivery credit values credit.Check in you system whether this table is updated with the delivery values for the credit account(customer number)
RVKRED77 u2013 Reorganize SD credit data
When updating errors occur, it enables you to reorganize the open credit, delivery and billing document values.
If the table is not updated run this report in background.
Regards,
Saju.S

Credit management and credit exposure

Hi experts,
Pls anybody clarify my doubt in Credit management.
I activated the credit control areas update as 000015(Open delivery and billing document value).And activated dynamic credit management "Automatic credit control".Now i explain with some example how it working. Fixed credit limit for customer A Rs.30,000/-, Receivables amount 22,000/-. Now if create a sales order for value >8000 i m not getting the credit lock waring messages.
(I.e) i am creating one sales Order for value Rs.9,000/-.(So credit limit crossed and not getting error msg or waring messages)
After that creating another sales order for same customer i am getting Warning msg like"Credit limit crossed_____amount".
So finally, CCR Rs.30,000/, Recei Rs.22,000/- but i can able to make even Sales Order value for Rs One lakh. I want here to block sales order should not be create.
Thanks in advance.
SR

When a sales order is created , only the confirmed quantity is taken for pending sales value even if sale order qty is more
Check OVA8 setting , open deliveries and open orders should be selected
You can set reaction status as warning or error.
Pricing procedure - Subtotal should be A . This will update structure s066
The above condition will work only for order creation . For sales order ammendment you have do the same setting for credit group 02.
If Dynamic credit check works with credit Horizon date . It is better to have static credit check.
Check MC30 after creating sales order whether structure s066 updated for the order.
check and confirm
Senthils

Error on Loading Credit Management Setups using iSetup in target instance

Hi All,
I am trying to migrate Oracle credit management functional setups(Scoring model, Checklist, Automation rules) from source instance to target instance. I am trying to achieve this by the usage of iSetup. Once the Load is done, I am getting the following error and the setups are not migrated. This error comes up only for Credit management Setups. Not for other functionalities. Please help me out on this.
+---------------------------------------------------------------------------+
Application Implementation: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
AZR12LOADER module: iSetup R12 Loader
+---------------------------------------------------------------------------+
Current system time is 09-OCT-2013 03:15:18
+---------------------------------------------------------------------------+
Concurrent Request Parameters
RELOAD_REQUEST_ID=
DBC_FILE_NAME=DEVF.dbc
SNAPSHOT_REQUEST_TYPE=E
SNAPSHOT_NAME=RAC Credit Management Test
RELOAD_METHOD=
REQUEST_TYPE=L
IS_REMOTE=Y
JOB_NAME=RAC Credit Management Test1
USER_NAME=DEPPS
Downloading the extract from central instance
Successfully copied the Extract
Time taken to download Extract and write as zip file = 0 seconds
Validating Primary Extract...
Parsing driver.xml
Time taken to parse the Driver file and construct setup objects:6 milliseconds
Sorting Apis based on their dependency...
Time taken to sort the Apis=12 milliseconds
Printing sorted Apis
Load Sequence 1
1)AR_CMGT_Scores
Oct 9, 2013 3:15:48 AM oracle.adf.share.config.ADFConfigFactory findOrCreateADFConfig
INFO: oracle.adf.share.config.ADFConfigFactory No META-INF/adf-config.xml found
Name: AR_CMGT_Scores
Type: BC4J
Path: oracle.apps.ar.ispeed.creditmgt.scores.server.ScoresAM
Time Taken(seconds): 2.0
Importing rows from xml file, and validating rows ......
Message not found. Application: AZ, Message Name: AZW_FWK_USER_ROW_EXCEPTION. Tokens: VONAME = Scores; KEY = Score Model Id = 'null'
; EXCEPTION = oracle.jbo.RowCreateException: JBO-25017: Error while creating a new entity row for ScoresEO.
java.lang.Integer incompatible with java.lang.Long
Message not found. Application: AZ, Message Name: AZW_FWK_USER_ROW_EXCEPTION. Tokens: VONAME = Scores; KEY = Score Model Id = 'null'
; EXCEPTION = oracle.jbo.RowCreateException: JBO-25017: Error while creating a new entity row for ScoresEO.
java.lang.Integer incompatible with java.lang.Long
Message not found. Application: AZ, Message Name: AZW_FWK_USER_ROW_EXCEPTION. Tokens: VONAME = Scores; KEY = Score Model Id = 'null'
; EXCEPTION = oracle.jbo.RowCreateException: JBO-25017: Error while creating a new entity row for ScoresEO.
java.lang.Integer incompatible with java.lang.Long
Message not found. Application: AZ, Message Name: AZW_FWK_USER_ROW_EXCEPTION. Tokens: VONAME = Scores; KEY = Score Model Id = 'null'
; EXCEPTION = oracle.jbo.RowCreateException: JBO-25017: Error while creating a new entity row for ScoresEO.
java.lang.Integer incompatible with java.lang.Long
Message not found. Application: AZ, Message Name: AZW_FWK_USER_ROW_EXCEPTION. Tokens: VONAME = Scores; KEY = Score Model Id = 'null'
; EXCEPTION = oracle.jbo.RowCreateException: JBO-25017: Error while creating a new entity row for ScoresEO.
java.lang.Integer incompatible with java.lang.Long
Message not found. Application: AZ, Message Name: AZW_FWK_USER_ROW_EXCEPTION. Tokens: VONAME = Scores; KEY = Score Model Id = 'null'
; EXCEPTION = oracle.jbo.RowCreateException: JBO-25017: Error while creating a new entity row for ScoresEO.
java.lang.Integer incompatible with java.lang.Long
Message not found. Application: AZ, Message Name: AZW_FWK_USER_ROW_EXCEPTION. Tokens: VONAME = Scores; KEY = Score Model Id = 'null'
; EXCEPTION = oracle.jbo.RowCreateException: JBO-25017: Error while creating a new entity row for ScoresEO.
java.lang.Integer incompatible with java.lang.Long
Message not found. Application: AZ, Message Name: AZW_FWK_USER_ROW_EXCEPTION. Tokens: VONAME = Scores; KEY = Score Model Id = 'null'
; EXCEPTION = Updates are not supported by this API.
74 rows processed, now posting changes to the database ......
Transaction committed.
Processed API:AR_CMGT_Scores
Status: WARNING
Concurrent program completed.
+---------------------------------------------------------------------------+
Start of log messages from FND_FILE
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
End of log messages from FND_FILE
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
Executing request completion options...
Finished executing request completion options.
+---------------------------------------------------------------------------+
Concurrent request completed
Current system time is 09-OCT-2013 03:15:50
+---------------------------------------------------------------------------+

Vivek,
Thanks for the update.
Regards,
Hussein

Info Structure S031 - Information on movement type categories

How can I find out the movement type categories for the S031 info structure? For instance what movement types add to the "Goods receipt" total or the "Goods issue" total. Also, how do you "switch off the updating process for specific, individual movements" as mentioned in the SAP documentation below.
The SAP documentation says:
"Goods movements are divided into the following types:
Goods receipt
Goods issue
Stock transfer
Transfer posting
Inventory differences
You can switch off the updating process for specific, individual movement types in inventory management or in one of the subsequent applications in the logistics chain."

Hi Sherry,
I had similar requirement. You have two options:
1. Just as you've known you can use the field "Statistically relevant".
With this indicator, you control whether a movement type is statistically relevant for Inventory Controlling or not.
In the standard system, all movement types are set in such a way that all material movements for the valuated stock and for the vendor consignment stock are updated.
2. You can define by statistic group:
As of Release 3.0C, there is a customer-specific enhancement that enables you to define a maximum of 4 statistics groups for each movement type. The name for the statistics group has four digits and is freely definable. With the help of the statistics group, you can individually update key figures of Inventory Controlling.
Example: Key figure Consumption and Range of coverage
In table T156, the movement types are characterized as relevant to consumption. Consumption is correspondingly updated in Inventory Controlling. In the information system, it can be useful for the user to interpret issue quantities (that is actually no consumption) as consumption in order to calculate the range of coverage of the material.
Example: A material is always transported into another plant by stock transfer. In the issuing plant, no range of coverage can be calculated because the stock removal quantity is not affecting consumption (movement type 351).
What is to be done in detail?
a) Maintain table TMCA via Transaction SM31.
b) Use SAP enhancement MCB10001 for Inventory Controlling.
Here, you can change the field contents of communication structures MCBEST and MCBEST according to your requirements.
In the above-mentioned example, the source code in the SAP enhancement would have to be as follows:
LOOP AT XMCMSEG.
* Kommunikationsstruktur Bestandscontrolling
IF XMCMSEG-STGRP1 = '1234'.
* Statistikgruppe 1234
* Menge Gesamtverbrauch
XMCMSEG-MGVBR = XMCMSEG-MENGE.
MODIFY XMCMSEG.
ENDIF.
ENDLOOP.
Please let me know if this helps you.
Regards,
Shawn.

How to Genrate Report On User defined Info-structure.

Dear Friends,
I have Info-structure having key figure as production order number, Production order qty and final comfirmation other that STD. I want to generate report but I don't want to go for the ABAP development. Is there any option we do have to generate reports.
Thanks and Regards,
Neel...

Hi Rajesh,
Yes COOIS is T-code where U could retrive any information regarding the production order. But I would like to know if I have info-structure how i could configure reports in STD-SAP. Since I managing the production in 2 units of measure one is Kg and other in Lit. In COOIS i able to get report in kg but I also want report in Lit.
Thanks in advance for ur suggestions.
Regards,
Neel

XI and Credit Management in FSCM 6.0

Hello,
We have ERP2005 with FSCM and want to use the Credit Commitment interface ( http://help.sap.com/erp2005_ehp_01/helpdata/en/43/2a1c518e5f601fe10000000a422035/frameset.htm ) to pass FI-AR data to SAP Credit Management via XI. The sender is the FI-AR system and the receiver is the SAP Credit Management system Both FI-AR and FSCM are on the same ERP2005 system and XI is on a seperate system.
I have downloaded the XI content for the the intefaces CreditCommitmentNotification_Out and CreditCommitmentNotification_In and set up the configurartion so messages come out of ERP and the determined receiver is the same ERP system but my problem is with the receiver communication channel. The SAP help link referenced above says I should be using the communication channel XIChannel. Can someone help me and tell me what type of communication channel this is and what I have to do set it up please.
Thanks in advance for your help.
Pete

Felipe,
Thanks for the info it solved the problem and the interface works now. For future reference in case anyone has the same problem the scenario is as follows
Sender                  = ERP (FI module)
Sender interface     = http://sap.com/xi/PI/FIN/Operational/Global
Sender namespace = CreditCommitmentNotification_Out
Receiver = ERP (FSCM)
Receiver interface     = CreditCommitmentNotification_In
Receiver namespace = http://sap.com/xi/FSCM/Global
No interface mapping is required just set up the receiver determination with receiver determination to use a receiver communication channel of type XI.
Thanks,
Pete

Configuring SAP Credit management interfaces in PI 7.0

Hi all,
I am working on PI 7.0 instance and have an issue while trying to connect Accounts receivable accounting with SAP Credit Management.
Did anybody configure this kind of interfaces (Credit cOMMITMENT & Credit Payment) so that they could be integrated with PI?
If so, could you please tell me the steps to configure the mappings and CCs in IR and ID?
i am following SAP Credit mngmnt config guide, but there is no info regarding this.
TCODES are: UKM_TRANSFER_ITEM & UKM_TRANSFER_VECTOR
Best regards,
David

try sapsr3.<table> instead of sap<sid>
SAPSR3 is the schema now. Once lock is removed , try to login with sap*/ddic with master password which you gave while installing.
Thanks
Prince Jose

Rebate, see rebate payments in user defined info structure (SIS)

Hi Gurus...i hope you can help me
The client need to see the rebate payments for each material in a user define info structure (S500) where the material is a characteristic of the infostructure and the payment is a ratio
I get to show the accrued value per material but no the payment
If the system show me the accrued value for at material level in a infostructure..i supose is possible to show the payment value?
I did create a S520 info structure as copy of S060, but when i try to create a update rule for the payment ratio the system show me the follow message
"Only source fields from MC communications structures allowed"
please let me kow how i did wrong....
tx a lot

Payments of rebates in SAP ERP are credit notes (billing documents).
Therefore you should see them in the sales infosystem as billing documents.
If you add the billing document type in the sales infostructure as a characteristic, then you will be able to report on rebate payments because they always have a specific billing document type.

User defined Info structure

Hi all
I am trying to create an infostructure of my own which will update document posting date after each transaction.
through mc21 I created an info structure under Inventory Controlling Event.
Created a separate update group for it.
Created update through mc24 & maintained required data-field
After generating the update I activated the infostructure.
maintained the user parameter MCL= X against my user profile.
now for testing I created ome material document through MIGO.
carried out update Log through mc30,but the the log is not showing my infostructure & not showing any data in table output also.
am not able to populate data in the infostructure.Is there anything remained for updating configuration?
Regards
Surupa

Hi Rajesh,
Yes COOIS is T-code where U could retrive any information regarding the production order. But I would like to know if I have info-structure how i could configure reports in STD-SAP. Since I managing the production in 2 units of measure one is Kg and other in Lit. In COOIS i able to get report in kg but I also want report in Lit.
Thanks in advance for ur suggestions.
Regards,
Neel

Info structures in credit management

Similar Messages

Maybe you are looking for