Link b/w credit horizon period and pricing proceadure

Hi Gurus
what is the link between credit horizon period and pricing proceadure.

Hi there,
Also check in OVA8 what is the horizion in Dynamic credit check for your credit control area.
Could be that the system is defaulting the horizion from there.
But as per standard, for your case system willnot check the orders that are due for delivery after 2 months. It will consider the orders that are due for delivery only within the 2 months of the order date.
So check the delivery due date is within the 2 months period or after the 2 months.
Regards,
Sivanand

Similar Messages

Credit Horizon Date and Sales Value in FD33

Hello,
I currently have the credit horizon for a certain risk category set to look at orders 7 days out in OVA8. The sales value in FD33 reflects open orders for the 7 days out, but is also adding 100% of a specific order type (dropship orders) regardless of the 7 day setting in OVA8 and is overstating the total credit exposure. I am wondering, what is the specific date field on the order that this "Credit horizon date" is referencing to do the 7 day calculation? My thought is that there is something different about this specific order type that the 7 day horizon is not seeing.
Appreciate the help.
Kevin Schuller

Hello Kevin Schuller,
I am also facing the same issue, can you please explain me how you closed this issue?
Your query is highly appreciated,
Regards,
Sadanand.

Table to link FI document number, line item and pricing condition type

Hi,
I am looking for tables to link the FI document number, line item and PO pricing condition type.
Appreciate any help on this.
Thanks.

For any PO in ME23n in which Goods receipt has happened, you can check in the itemdetails->Po history tab in ME23n.
Here you will find the material document number. Just click on the material document, it will take you to anpther screen here you will find a button for FI document.
Click that button for FI document. In PO history istelf you can see the Condition types.
Hope this helps.

Link between Credit Risk Category and Terms of Payment

Hi,
Is there a link between the Credit risk category and the terms of payment. Where can we maintain this.
For instance, if risk category is x, the top is a, risk category is y, top is b.
Please suggest.

There is no link between credit risk category and Terms of Payment. The Risk Category is assigned to credit limit of the customer which determines if it will be blocked at certain level for sales transactions or just a warning message that the customer is over the limit. For the terms of payment, it just determines when it's due or whether it's overdue or not.

Customer Credit control limit options Period and Value

Hi All,
Can any body suggest or help regarding my requirement.
I know the standard credit management process which is based on the credit limit Value which will be maintained in the FD32.
But My requirement is
-->Credit limit based on the period
-->Credit limit based on the value.
-->Credit limit based on the period and value.
1.If I activate credit limit based on the period,customer order should be blocked when the customer exceeds 15 days credit limit- is there any standard option on this
2.If I activate Credit limit based on the value,customer order should be blocked when the customer exceeds credit limit value which is maintained in FD32.
3.If I activate Credit limit based on the period and value,customer order should be blocked when the customer exceeds credit limit period and value.
Is this possible in the standard credit management !
or this is possible only through workaround
Provide me the document if available
Regards,
Murali.

Hi all,
In addition to previous requirement.
We also need to take consideration under scenario also.
For example
One customer taken the goods from 1st to 15th, actually he has to pay the credit amount on or before 30th if he is not able to pay on 30th system should block the further sales orders(i.e. from next month 1st onwards).
is this option available in he standard !
Can any body help on this ASAP.
Regards,
Murali.

Regarding Horizon period in Dynamic Credit Check

Hi All,
i am using a dynamic credit management with horizon as 1 month, suppose consider todays date ( 11th May), as per the configuration, the system should block the documents that has Material availability date till 10th or 11th June, but am getting credit holds even beyond this period, say for the MAD on 30th June too.
am i missing something on the configuration part, also please let me on the ways of changing the horizon period to days from months, currently this field is marked as non-editable & is seen in grey.
Thanks & Regards
Ilango

Hi
no the horizon period is calculated from the Material availability date, please refer to the SAP note 447919
The relevant date for the dynamic credit limit check is NOT the shipping date, BUT the material availability date of schedule line VBEP-MBDAT.
This also concerns the time horizons in reports RFDKLI40 and RFDKLI41 and in Transactions FD32 or FD33.
and my question is to understand does it consider the June month fully or strictly the 30/31 days from the current date for 1 month horizon as on 10th may 2010.
Thanks & Regards
Ilango

How can we change horizone period from Months to days in credit management

Hi SAP SD gurues,
                              Can anybody tell the procedure "how to change Horizone period from months to days in credit management in "OVA8" . As you may get month is greyed out in horizone period settings. Advance Thanks with warm regards.
                                                                      Kartik

Dear Sadhu,
                  Sorry still i am not satisfied with your answer.As you hav told to go through the TC OVBI, there i found it is no where or little related to Horizon period of Credit management of SD module. In OVBI it is meant for "Maintain Billing plan type for Period Billing". Yes there is a combo box called "HORIZON", but i believe the purpose of this Horizon is diffrentthan the "Horizon period in SD Credit management. Pls correct me and explain me how it is related if i am wrong. Hope you'll do so.Thanks for yr valuable reply.Kartik...

Update S066 and S067 tables after changing the credit horizon

Hi,
I have changed the credit horizon which was previously month to day through OMO1. However after making this change, all the contents of credit management in the table S066 and S067 were deleted. Is there a way to update the the tables after this change has already been made? I tried using the programs RJ-JANEU and RJ-JFNEU, by slelcting the checkbox Reorganize credit data, however I get a message stating No orders/Billing documents to be updated were found.
I would appreciate if someone could guide me through the process that needs to be followed. Thank you for your help in advance.
Regards,
Sandeep

Success
The connection test was successful.
=============
Information from Review Screen:
Name Value
Oracle home path /u01/app/oracle/product/11.2.0/dbhome_1
Monitor Username dbsnmp
Monitor Password ******
Role NORMAL
Listener Machine Name urora2t.unioncentral.com
Port 1526
Database SID finapp1t
Preferred Connect String
Edited by: sawright on Mar 29, 2012 11:24 AM

MIGO/GR w/ PO and Validity Period Specific Pricing

We have a business requirement to maintain validity period specific pricing on our outline agreements (Scheduling Agreements/Contracts). The question is can receiving be controlled to pick the correct price based on delivery date and not when the goods are actually received?
Example:
Part A
4/10/2014 to 4/20/2014 - $4.00
4/21/2014 to 4/30/2014 - $5.00
Scenario #1- Contract--> Release PO
This scenario is working correctly due the release purchase order pricing is referenced based on when the purchase order is created.
Scenario #2-Scheduling Agreement-->Delivery Schedule
During the prototype, when setting up a validity perios specific price as above, the price is only taken into account at the start of the validity period.
If the delivery schedule line says 4/18, but it's not received until 4/22, SAP will pull the 2nd validity period price instead of the 1st period. Is there a way to ensure that the correct validity period gets pulled?

I think its possible, though i did not check for Scheduling agreement but it works for PO
Can you please explore Vendor master>Purchasing Data> Pricing Date Control field options
It should help
Thanks
DD

Linking a Period Indicator to a Posting Period and Document Numbering

Dear All,
Could you please tell me that, what will be the consequences if I do not link a Period Indicator to a Posting Period and use the Period Indicator in any document numbering?

Hi,
The use of the period indicators depends on the accounting practice of the company.
The consequence you will face when you are not using period indicators:
1.Your document numbering series will be continued from year to year,for ex.if your last document numbering series for AP Invoice is 3489 for FY200809,then the starting series for the FY200910 will be 3490.
2.You should perform period end closure before proceeding to the next financial year,which would not be possible(Atleast one month in the new financial yr) as we may need to use adjustment transaction for accounting/auditing purpose
3.Unless you perform year end closure the new series can not be continued,if you continue there must be accepted/explained in the accounts auditing too .
4.But you don't use period indicator,there will not be any necessity to create new document series for every new financial year.
Also check this document on [Period indicators|https://websmp105.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000513532005E] for better understanding.
Hope this is helpful!

Credit Card config and encryption

Hi frnds
I would appreciate if anyone can provide the config steps for credit card and also the step for encrytion. If you have a doc on it then please mail it to [email protected]

hi
CREDIT CARDS
Go thr below links:
PAYMENT CARDS:
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/SDBILIVPC/SDBILIVPC.pdf
http://help.sap.com/saphelp_erp2005vp/helpdata/en/93/745309546011d1a7020000e829fd11/frameset.htm
Overview
This document attempts to explain in the brief the credit card processing in SAP.
SAP provides a flexible and secure payment card interface that works with the
software of selected partners that provide merchant processes and clearing house
services. In SAP the credit card processing is integrated with the sales and
distribution module.
Payment card configuration
Much of what is required for credit card processing to work with VISA, Master
Card, and American Express is already set up in SAP.
For all credit card configurations refer to
Define Card Types
Transaction SPRO IMG ‡ Sales and Distribution ‡ Billing ‡ Payment Cards
Here we define the type of cards that can be used in the system. A four-letter
code is given for each card type. E.g. MAST for Master Card, VSAJ for Visa
Japan. A function module for checking the card number is also specified here.
1. Define Card Types
Credit Card Configuration And Processing In SAP
Maintain Card Categories
(a) Define card Categories: Here we specify the card category of the
payment card. With this the system automatically determines the card
category when you enter a card number in master data or sales
documents.
(b) Determine card categories: Here we specify the acceptable number
ranges for different card types. Also card categories are assigned to the
card types. Even though SAP comes with card checking algorithms
(Function Modules) for standard card types this configuration setting
is particularly useful to those cards that do not contain any standard
checking algorithm already set up in SAP.
2. Determine Card Categories
Maintain Payment Card Plan Type
In this step, you assign the payment plan type for payment cards, the payment
card plan type, to all sales document types in which you will be using payment
cards. You cannot process payment cards if you have not made this assignment
The standard system contains payment plan type 03 for processing payment
cards. 3. Show the screen where this assignment is done.
Credit Card Configuration And Processing In SAP
3. Maintain Payment Plan Type
Maintain Blocking Reasons
In this step, you define blocking reasons for payment cards. You enter these in
the payer master record to block cards. The standard system contains blocking
reason 01 for lost cards.
Risk Management for Payment Cards
Transaction SPRO IMG ‡ Sales and Distribution ‡ Billing ‡ Payment Cards
‡ Authorization and settlement ‡ Risk Management for payment cards.
Risk Management plays a central role within Sales, providing you with checks
and functions to minimize your credit risk. In addition to letters of credit and
export credit insurance, payment cards are among the payment guarantee forms
that you can use to insure payment for sales order items. SAP comes with predefined
payment forms of guarantee as shown below. Customer can also
maintain other forms of payment suited for their line of business.
Credit Card Configuration And Processing In SAP
Define forms of payment guarantee
3. Define forms of payment guarantee
Maintain payment guarantee procedures
In this step, you define Payment guarantee procedure. These procedure controls,
which form of payment guarantee, are valid for a particular customer, and for a
particular sales document type.
The various settings done under this configuration are
Define payment guarantee procedures
Maintain customer determination procedure
Maintain document determination procedure
Assign sales document types
Determine payment guarantee procedures
Maintain authorization requirements*
Here requirements* are set to tell the system how and when to carry out
authorization when a sales order is saved. SAP comes with two requirements
Form routine 1. Carry out authorization only when the sales document is
complete. The system carries authorization when the order is saved.
Form routine 2. Carry out authorization only when the sales document is
complete, but the authorization for all the complete documents is carried out in
batch.
Additional requirements* can be assigned here as per the business requirements.
*Requirements are ABAP/4 code. Requirements for various functions can be accessed using transaction VOFM
Credit Card Configuration And Processing In SAP
4. Maintain Card Authorization Requirements
Maintain Checking Groups
How and when authorizations are carried out depends on the setting you make in
the customizing for maintain checking group routines.
The three main settings that influence authorization are:
a) Authorization requirements
b) Authorization horizon
c) Preauthorization
There are two settings under this setting.
Define checking group: Here a checking group is defined and the
authorization requirement (described in the previous section), Authorization
horizon (described below) and preauthorization settings are done for this
checking group.
5. Define Checking Group
Credit Card Configuration And Processing In SAP
Here you can see a checking group C1 is defined with the authorization
requirement 902. Checking the pre-authorization tells the system to carryout preauthorization
if the order fulfillment date falls outside the horizon. The
authorization horizon specifies the number of days before the material
availability date, or billing date, that the system is to initiate authorization. If a
sales order is saved within the authorization horizon, the system carries out
authorization immediately. If a sales order is saved before the authorization
horizon comes into effect, the system does not authorize at all, or carries out
preauthorization.
6. Preauthorization Concept
In this example, the system has been set to authorize one day before delivery
creation. The system does not carry out authorization when the order is saved on
Day 0, rather on Day 2. Note that the authorization validity period has been set to
14 days in Customizing IMG‡ Authorization and settlement‡ Specify
authorization validity periods. The transaction will have to be reauthorized if
delivery activities take longer than 14 days.
Assign checking groups: Here the checking groups defined earlier are
assigned to different sales document types as shown 8.
Specify authorization validity periods
Here number of days that an authorization can remain valid for different card
types are maintained. Refer to 9.
Credit Card Configuration And Processing In SAP
8. Assign checking groups
9. Assign validity period for authorization for different card types
Credit Card Configuration And Processing In SAP
Account Determination
Transaction SPRO IMG ‡ Sales and Distribution ‡ Billing ‡ Payment Cards‡
Authorization and settlement ‡ Maintain Clearing House
In the following steps, you set the condition technique for determining
clearinghouse reconciliation accounts for authorization and settlement. The
system uses the entries here to determine the clearing account for the payment
card charges. When settlement is run, the postings in the receivable account for
the payment card will be credited and a consolidated debit will be created and
posted to the clearinghouse account. These accounts are a special type of general
ledger account that is posted from Sales and Distribution.
Here, you maintain:
• Maintain field catalog.
• Condition tables and the fields that they contain
• Access sequences and condition types
• Account determination procedures
• You then assign these accounts to condition types.
Add to field catalog
Here you maintain the fields that can be used in the condition table. 10.
Shows the transaction to maintain the field catalog.
10. Maintain Field Catalog.
Maintain condition tables
Here condition tables are maintained with fields that are added to the field
catalog. SAP comes pre-configured with two condition tables 4 and 6. Refer
11.
Credit Card Configuration And Processing In SAP
11. Maintain Condition Table
Maintain access sequences
In this step we define an access sequence and link the access sequence with the
condition tables.
Here an access sequence is defined. SAP comes with the access sequence A001.
12. Define Access Sequence
Once the new access sequence is defined, it is linked to the condition tables as
shown in the next screen.
Credit Card Configuration And Processing In SAP
13. Maintain Access For Access Sequence
Selecting an access and clicking fields will display the fields for the selected
access as shown below for access 10 as shown above.
14. Display Access Fields
Maintain condition types
Here condition types are defined and the access sequence to linked to it.
Condition types are contained in account determination procedures and control
which access sequences the system uses to find condition records.
These are The condition tables.
Credit Card Configuration And Processing In SAP
15. Define condition type
Maintain account determination procedure
In this step an account determination procedure is defined and linked to the
condition type (which in turn is linked to the access sequence).
Define account determination procedure
16. Assign account determination procedure.
Here an account determination procedure CC01 is defined and the condition type
CC01 is assigned to it.
Access sequence linked to the condition type
Credit Card Configuration And Processing In SAP
Assign account determination procedures
In this customizing the previously set up account determination procedure is
assigned to different billing documents.
Assign Accounts (G/L)
G/L accounts are assigned here for the combination of Sales organization, Card
type, chart of accounts and condition types as shown in the 17.
17. Assign G/L accounts
Set authorization / settlement control per account
Each G/L account is assigned an authorization and a settlement function module.
The system will read the configuration a call the authorization and settlement
function module during authorization and settlement respectively.
Credit Card Configuration And Processing In SAP
18. Set Authorization and settlement function module
Maintain merchant IDs per account
A merchant may have one or more IDs for each clearinghouse with which it does
business. Here, you assign these different merchant IDs to their related
receivables accounts.
19. Assign Merchant ID’s
Credit Card Configuration And Processing In SAP
Authorization and Settlement in SAP
20. Sales Order Cycle With Credit Card Authorization
When an order is placed through the front-end system, the order information,
credit card information, billing information, shipping information is passed to
SAP. SAP processes the order calculates the taxes, the shipping costs and reads
the configuration information settings and executes the function module setup as
described in Fig. 18. The function module formats the data and makes a RFC *
call to the payment application**.
The payment application screens the order for fraud, encrypts the data and
communicates with the third party processor who in turns communicates with
the card association and card issuer.
*RFC (Remote Function Call)
*Payment Application: Middle ware between SAP and third party processor/bank.
Credit Card Configuration And Processing In SAP
The third party processor responds back with the response whether the
transaction is approved or declined or referred.
Note: When any item in the order does not have a confirmed quantity, then
authorization is not carried out for the full amount. A small dollar amount
usually ($1) is used as the authorization amount. During the rescheduling run
the system will check for the material availability. If the material can be
delivered within the horizon date, a full authorization for the order is carried
out.
Approved: When the credit card transaction is approved the systems checks for
the material availability, confirms the material for the ordered quantity and saves
the order.
Declined: The material availability check for the material is not made, and the
order is rejected.
Referred: The order is saved and is blocked for delivery. In this situation is
merchant calls the bank checks for the available credit on the card and a manual
authorization is carried out.
21. Sales Order Entry Screen in SAP
Payment Card
Information
Credit Card Configuration And Processing In SAP
The first line in payment card screen is the card check performed by SAP system,
using the card check algorithm function module as described in 1. And the
remaining lines represent the actual authorizations that are carried out.
22. Payment Card Screen
Path Header ‡ Payment Cards.
Settlement
Legally the merchant can charge the credit card after the order has been
completely processed. In SAP this happens after a delivery is created and the
goods has been shipped. In case there is not enough authorization for the order
to be delivered, the system goes out the get the authorization for the remaining
amount.
In SAP settlement is initiated using the transaction FCC1. All the valid
authorization is submitted in a batch to the payment application at scheduled
intervals as specified by the third party processor.
The payment application encrypts this data and communicates with the third
party processor. The third party processor checks if the settlement request has a
valid authorization against it. The third party processor then transfers the fund
from the cardholder’s bank to the merchant bank.
Authorization
Response
Credit Card Configuration And Processing In SAP

Sales Orders Outside Credit Horizon

Hi everyone,
My client has implemented FSCM credit management, using a Dynamic credit check with a 6-day credit horizon.
It was my understanding that for an order where the material availability date of every schedule line is outside the credit horizon, then no credit check is performed on the order. During testing, it seemed to behave this way--if an order was outside horizon, the credit check status on the order header said "Not Performed" until it entered the horizon, at which point a check was performed by RVKRED08.
What I am seeing now is that every order undergoes a credit check at entry, and receives an "Approved" or "Not approved" credit status. Orders ouside horizon will always be approved if the customer is below their limit, and are always be blocked if the customer is above the limit. Does anyone have an idea why SAP did not credit check orders outside the horizon?
Thank you!

Hi David,
If an order was created today with the delivery date after 6 days(lets assume the horixzon period is 6 months).
so taking this perticular order in consideration during credit check will reduce the customer's credit availability. To insure that customer can place current orders with the business, either business will have to increase his credit limit or block the order and negotiate with customer to pay the previous dues, this option is risky as customer enjoys high credit limit and also wouldnt like to be blocked for the orders which he may need in less than 6 days.
So due to horizon , this order will not be considered in the dynamic credit check as shipping is beyond the horizon, and customer can place new orders within his allocated credit limit. Ensuring for a business to keep credit limits to optimum level and continuous business.
I hope that gives you clear view.
Please close the thread if answered.
Regards,
Paresh Kolte

Sales orders due for delivery beyond credit horizon date credit blocked

Hi
I have given credit horizon date as 1 month . When I create a sales order which has a single item and schedule line with delivery date after 45 days i.e clearly after the horizon date , document is blocked with credit limit block .
I am actually testing the cycle after I changed credit horizon date from 3 months to 1 month .
Is there any thing else to be done like running any reprort , etc ?
Regards
Raghav SSk

Hi,
I had the same problem. The Horizon the 1 month mean that every sales order that entry in the systen during the month, will be affected the credit exposure.
For example.
Today is 02/july and my horizon are 1 month, so the date are 01/august. Every sales order tha entering in period between july and august will be affect the credit exposure. The sales order entering in 05/august, the credit will be affected. The sales order entering in 30/august, the credit will be affected, but if you enter the sales order in 01/september the credit will not be affect beacause the month is different.
Another example
Today is 02/july and my period are 2 months, so the date are 31/august. Every sales order that entering in period between july and august will be affect the credit exposure. If a sales order entering in 01/september, the credit exposure is not be affected, because the month is different.
Regards
Paulo

SD CREDIT MANAGEMENT - CUSTOMER AND PERIODWISE

Dear All
We need to maintain the PERIOD WISE as well as CUSTOMER WISE Credit Management , If it is possible ,please sent us the complete config document of the same.
Regards
Animesh Chakraborty

Hi,
period wise u can use in ova8 .in sesional factor can be used .u have to do customer wise u can do with FD-32 .
PLEASE REFF THE NOTES IT MAY USEFULL FOR U.
How To Do Configuration For Credit Management
Credit and risk management takes place in the credit control area. According to your corporate requirements, you can implement credit management that is centralized, decentralized, or somewhere in between.
An organizational unit that represents the area where customer credit is awarded and monitored.   This organizational unit can either be a single or several company codes, if credit control is performed across several company codes. One credit control area contains credit control information for each customer.
For example, if your credit management is centralized, you can define one credit control area for all of your company codes.
If, on the other hand, your credit policy requires decentralized credit management, you can define credit control areas for each company code or each group of company codes.
Credit limits and credit exposure are managed at both credit control area and customer level. You set up credit control areas and other data related to credit management in Customizing for Financial Accounting. The implementation guide is under Enterprise Structure -> Definition or Assignment -> Financial Accounting and then Maintain credit control area. You assign customers to specific credit control areas and specify the appropriate credit limits in the customer master record.
Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into account according to their priority. The credit control area found is stored in field VBAK-KKBER.
1. Transaction OB38
   Check which credit control area is assigned to the company code.
   Company code:
   Credit control area:
2. Transaction OVFL
   Check which credit control area is assigned to the sales area.
   Sales area:
   Credit control area:
3. Transaction XD02 or VD02
   Check which credit control area is assigned to the payer.
   Payer:
   Credit control area:
4. Transaction SE37
   Is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
   For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
   OB45, or the credit control area must be entered under the relevant company code in table
   T001CM of the credit control areas allowed.
   Company code:
   Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
   Which settings do exist for the sales document type used?
   Sales document:
   Check credit:
   Credit group:
8. Transaction OVAD
   Which settings do exist for the delivery type used?
   Delivery type:
   Credit group for delivery:
   Credit group for goods issue:
9. Transaction OB01
   Credit management/Change risk category
   Definition of the risk category for each credit control area. This risk category can be
   assigned to a credit account by using Transaction FD32.
10. Transaction OVA8
    Here, the individual credit checks for key fields
    o credit control area
    o risk category
    o credit group are set. Take these key fields from the above settings and go to the detail
      screen. In particular, check whether fields "Reaction" and "Status/block" are set
      correctly. To carry out follow-up actions in case of a credit block, the credit check
      status must be set (field "Status/block").
11. Transaction FD32
    Credit master data for the payer of the relevant document.
    Credit account:
    Credit limit:
    Risk category:
    Currency:
12. Settings for updating the credit values Update of the credit values is required for the limit
    check (static or dynamic credit limit check).
13. Transaction OVA7
    Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to
    field "Active receivable" in Transaction VOV7.
    Item type:
    Active receivable:
14. Transaction V/08, Pricing
    In the pricing procedure used for pricing, subtotal "A" must be entered in a line for
    determining the credit value (mark the pricing procedure and doubleclick on "Control").
    Usually, the net value plus taxes is used. This way the system is determined to use this
    subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for
    update and credit check.
    You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
    Pricing procedure:
    Line with subtotal = 'A':
15. Transaction OB45
    Which update group (field "Update") do you use in the relevant credit control area? The
    default setting is "12". If you use another update group, check whether this is fine with
    you. If you open an OSS message, please tell us the alternative update group.
    Credit control area:
    Update:
16. Transaction OMO1
    Which kind of update did you choose for structure S066?
     In any case, "Synchronous update (1)" has to be chosen as the kind of update.
     All other settings will lead to errors.
Best regards,
venkataswamy.y
Edited by: yanamadala venkataswamy on Dec 10, 2008 3:11 AM

I tried to download a movie on my iPod touch but due to limited space, it did not download. Then, I checked my credit card online, and I found the money was already taken. How will I get it to download on another device with the same account?

I tried to download a movie on my iPod touch but due to limited space, it did not download. Then, I checked my credit card online, and I found the money was already taken. How will I get it to download on another device with the same account? Also, I was wondering why they took my money even when it did not finish downloading let alone get downloaded?

Welcome to the Apple Community.
You can re-download content purchased from the iTunes store (availability varies depending on location) using the purchased option from the Quick Links section in the top right corner of the iTunes homepage in your iTunes application on your computer.
You can re-download content purchased from the iTunes store (availability varies depending on location) using the purchased option which is revealed in the iTunes app on your iOS device by tapping the more button at the bottom of the screen.

Link b/w credit horizon period and pricing proceadure

Similar Messages

Maybe you are looking for