Customer Master - Debit Notification Preferences

In the Customer master, on the Payment Details tab, there is a section at the bottom called "Debit Notification Preferences", under which I can choose a delivery method (email, fax, printed) and then enter the corresponding information (email address, fax #).
Is this information actually used anywhere? It leads me to believe that there's a tool that will look at this information and automatically email or fax an invoice. Or is it purely for reference purposes (and for building your own delivery/transmission tool)?
I've been unable to find any information in the AR user/reference/imp guide, TCA guides, etc. Any information would be much appreciated.
Thanks

The debit notification preferences specify the mode of communication to the customers about the payments received from them.
I have requirement that, based on this field I have to do bursting. if its email , copy should be emailed and if its fax we should be Faxing it.
Though I am having difficulty finding the table which stores it. any help?

Similar Messages

Notification when customer master range exceesd 95%

Hi,
Our customer master number range was almost over.....
Luckily we noticed it and we extened the number range.
So we are planning to set up a notification such that it notifies via email when customer master number range is used 95%.
Any of you have set up this notification .
Can you pleas provide any inputs.
Thanks for the help

Build a Custom Program that would check the 'Current Number' for the Customer Master Number Range and that would send the Notification if the current number is 95% of the whole number range . You can set this program as a background Job daily/weekly/monthly based on your need.

Customer master workflow

Hi Experts,
We are developing a customer master workflow, when ever customer master record is created the workflow will be triggered.
This triggering event is mapped to the change doc object debi.
My concern is i want to raise this event at sales org or company code creation level.
I tried doing this validation at check function module,however the record gets already created & updated in tables. So im not able to validate at this point.
Please advice , how can we achieve this.
Thanks in advance for your inputs.
Regards
Keerthi

Hi,
If you are using a Webdynpro alpplication ... then it would be easier.
There should be "Create" button. In the WDA this button is linked with a action-method.
Now write down the code to start workflow. You can use the following method to start a workflow.
SWW_WI_START_SIMPLE : General Task not required
SWU_START_WORKFLOW : General Task not required
SAP_WAPI_START_WORKFLOW : General Task Required
EWW_WORKFLOW_START : General Task not required
Now design the workflow as per your requirement ( single level / multiple level ). after all approval call a FM to save in the IT, if rejected this FM should not be called. You can also set up the notification to the initiating user to notify the approval/rejection by the approver.
Hoping that this might help you.
Thanks and regards,
SNJY

Need Business case Explaination about the Field in Customer Master

Hi all,
I have a doubt in Customer master Record
1. Customer Group
2. Price Group
3. Price list
4. Customer Stat.group
What I mentioned above fields i need business case explination, but all the above fileds are explaining about the Price and Statistics about the report. By using F1 Help i can understand but i need business case
Is there any link between those fields ?
@ Please dont close the thread if it is basic question please provide the details and link because i serached in Google but i couldn't able to findout

hi
anuradha,
In my knowledge customer pricing group is the main in the customer master ,
you will one test case in customer pricing group in customer u can not fill it, the same customer u can rise the sale order , system sows earorr message, no customer master records maintain, it means when u create the sale order system take pricing procedure , pricing procedure determination ; sales area+customer pricing procedure +document pricing procedure assign to pricing procedure,(ovkk) ,
customer statical group
Sales Organization      0001   Sales Org. 001
Distribution Channel    01
Division                       00
Cust.stats.grp              1      'A' Material
CustGroupMaterial       1      'A' Material
StatGrpSalesDoc         2      Returns, Credit Memo
StatGrpDocumentItm     1      Returns, Credit Memo
Update Group               1      SIS: Sales Document, Delivery, Billing Document
it is the static updating group for item level,
Sales Organization     0001   Sales Org. 001
Distribution Channel    01
Division                        01
Cust.stats.grp             1      'A' Material
StatGrpSalesDoc        1      Order, Debit Memo
Update Group              1      SIS: Sales Document, Delivery, Billing Document
it is for static updating group for header level
it is use full in vov7 ,
price list and price group it is use full pricing to the customers, you can check it sale order header in sale tab u can find your required fields,

Add a custom button on notification page and open a oaf page after button

Hi All,
My Requirement is add a custom button on notification page and after button click with take some parameter from notification page like supplier_id and org_id then open a new oaf page and show supplier credit and debit balance but problem is that button is only enable to a ap invoices notification not for other type of notification.
how to take approach/action i don't know.
it is possible through OAF personalization/customization or it is part of work flow customization.
Navigation path - payable->worklist->open notification and Type of notification also there
Type should be matched with AP_Invoices type notification then custom button enable.
Please Let me know is it possible or not. If possible how to achieve this. ...................................it's argent...plz help me
Edited by: 815572 on Nov 25, 2010 1:15 AM

Hi Irk,
My notification came in given below format (in table) but my custom button only enable for Contract Approval Type not for others..........i hv attach a button on notification page (subject-Contract 21969-R17......)
From Type Subject Sent
Taylor, Phillip Contract Approval Contract 21969 - R17-AUG-07 06:19:27 has been approved by Taylor, Phillip 22-Aug-2007
Taylor, Phillip OKS Contract Process Contract 21975 - R17-AUG-07 06:22:18 for AT&T Universal Card (52,500.00 USD) has been published online 19-Aug-2007
Taylor, Phillip OKS Contract Process Contract 21969 - R17-AUG-07 06:19:27 for AT&T Universal Card (15,000.00 USD) has been published online 19-Aug-2007
If I just put a button SHOW BALANCE just like notification button APPROVE, REJECT, REASSIGN but this button shows all types of notification and my req. is this button show only for Contract Approval type notification. how to handled this issuesss ?
if extend the co of notification page then how to handle TYPE value from worklist page ....please write proper code if u hv any idea...........
Thanks,

Report needed: Customer master TAXKD field changes

We are looking to track changes made to TAXKD (tax code) in customer master.   Is there any report we could generate weekly that would detail changes made to the field.
Also, we'd like what change was made. (i.e. customer number, date, field changed from 0 to 2)
Thanks,
Michelle

Hi Michelle,,
Those changes will be recorded in the CDHDR and CDPOS tables with your field name based on the dates..
and also with the Old value and the New value
from the CDPOS
pass
OBJECTCLAS = 'DEBI'.
OBJECTID      = Your document number "optional
TABNAME    = 'KNV1.
FNAME       =   'TAXKD'.
if you pass these thins you will get the in the fileds VALUE_NEW and VALUE_OLD
hope these informatino useful to you.
Thanks
Edited by: Prasanth on Apr 13, 2009 7:40 PM

Payment term in customer master

Gurus,
XD02 - Change Customer Master
Payment term is maintained in
=> Company code data -> Payment Transactions -> Payment Data-> Payment term
=> Sales Area Data -> Billing Documents-> Delivery ad payment terms-> Terms of payment
In sales order, system propose payment term from Sales area data.
Please explain importance of these field.
Regards,
Ashish
Edited by: Ashish Desai on May 4, 2009 2:57 AM

Hi
In addition to all the suggestions given by all friends
If the invoicing is done thro SD route that is VF01 then the terms of payment maintained in sales area data will get preference
If the invoicing is done thro FI route that is FB70 then the terms of payment maintained in company code data will get preference
If the credit management is active then the terms of payement maintained in company code will take the control
For easy understanding as long as credit management is not active the terms of payment in sales area data will have the control as we are not going to touch FB70 at all mostly
As said by all others terms of payement is taken from payer
Regards
Raja

Customer Master - ADRNR field details.

Hi SDiens,
This is regarding Customer Master data.
Use T-code "SE16" then enter Table Name "KNA1" to see values for any particular Master record for eg. 1000.
In this you will find some Values in field "ADRNR, MCOD1, MCOD2". whereas if you open the same record with "XD02" you cannot see this values.
Even I am not entering this vause while creating records using "XD01". Can someone explain where can I see this Values.
Matter urgent.
Helpful answers will be rewarded.
Cheers
RC

Hi,
I looked in to this issue and got this information sto you please go through ADRNR number is the number provided internally by the system.and the remaining 2 fields MCOD1, MCOD2 are there in General data tab.
Address number
Internal key for identifying a Business Address Services address.
For more information about the meaning and use of the address number and the Business Address Services concepts, see the function group SZA0 documentation.
Business Address Services
I. General
You can manage addresses conveniently using a standard function module interface with Business Address Services. There are interfaces for maintenance with or without dialog and an address maintenance transaction.
Address attributes
An address in Business Address Services is a complex attribute of a primary object which saves only the reference to the address key. (In certain constellations, controlled redundancy is possible).
The address management distinguishes between addresses on the basis of time dependency and international formats.
The database structures allow for the date-dependency of addresses, but all function modules currently use date-independent addresses (the default validity range is 1.1.00001 - 31.12.9999).
Address types
Addresses are distinguished according to the application context in which they are used:
"Normal" addresses (Address type 1): This type of address can either be associated with an application object or be on its own.
Typical examples are the addresses of organizational units (for example, company code, plant), delivery address, functional location, and so on.
Such an address is identified in the DB by a 10-digit address number.
Examples: company code 0001 has address 4711
          customer MIKE has address 5678
Private addresses of persons (Address type 2): These are addresses which are assigned to exactly one natural person, with extended attributes compared to the normal addresses (title, part of name, etc.) for the person. The person with the address-relevant attributes is an independent object, which is maintained in Business Address Sercices.
Personal addresses are assigned to exactly one person, and can not be referred to by other application objects. The complete address object (person with address) can have several uses.
For identification, a 10-digit number for the person and a 10-digit number for the address are required.
A person (identified by the 10-character address) can have several addresses.
Example: business partner CHARLY is a natural person and has two addresses:
a) the first address is identified by person number 1234 and address number 3333.
b) the second address is identified by person number 1234 and address number 3357.
Addresses of persons in companies (Address type 3): These are addresses which contain the properties of a person in a company, with attributes such as Department, room number, extension.
Any normal address (address type 1), but not a private address, can be the company address.
The address of a person in a company is identified, like a private address by a 10-digit number each for the person and for the address.
Example: business partner CHARLY (see above) is contact person at business partner SAP_AG with company address 4444; CHARLY's contact person address is identified by person number 1234 (see above) and address number 4444.
These three address objects constitute an abstract data structure. The function group SZA0 contains function modules for accessing these address types. There are function modules for maintenance (create, change and delete), and to read and to search for each address type. There are also function modules to maintain and read all communication types which are supported by R/3, for each address type.
Function modules for private addresses begin with the prefix 'ADDR_PERSONAL_', those for addresses of a person in a company begin with 'ADDR_PERS_COMP'. Other function modules which begin with 'ADDR_' are for normal address maintenance, or in some cases, function group management.
The function modules manage the data structure using a maintenance interface. The underlying tables must not be accessed directly. This could lead to inconsistencies in data structures which contain fields from several tables.
Address maintenance
Addresses should be maintained as far as possible using standard dialogs which are available in other function groups.
Popup, subscreen and full screen dialog techniques are used.
The parameter transaction SADR can also be used for maintaining normal addresses which do not depend on an application object. These addresses cannot be distributed by ALE.
For more information, see the SZA1, SZA5 and SZA7 function group documentation.
For information about address validation see the documentation of function group SZAR.
If addresses are to be maintained without dialog, or if a user maintenance dialog is necessary for special requirements, addresses can also be maintained directly using the function modules of the function group SZA0. The standard dialogs of the function groups SZA1, SZA5 and SZA7 are also implemented with them.
Conversion of existing SADR/SADRP addresses
Most old addresses will be converted for the new central address management (Business Address Services) for Release 4.0.
From Release 4.5, all SD document addresses (previously SADR), customer addresses (previously only KNA1), supplier addresses (previously only LFA1), business and private addresses of (customer) contact persons (previously SADR) and bank addresses (previously SADR) will also be in Business Address Services (central address management).
Release notes Central address management for 4.0A and Central address management in Release 4.5 contain detailed information.
II. Maintenance without dialog (function group SZA0)
The contents of the function group can be classified as follows: management modules, which either apply to the function group as a whole or ensure correct database storage, address object maintenance (create, change, delete) modules, and address object communications address processing, for example, telephone, fax, or mail addresses.
Organization
Local memory:
Save
ADDR_MEMORY_SAVE: Saves the local memory contents in the database. All address data changes made since the first call of any function module in the function group are then permanent. Numbers must have been assigned to all addresses and persons before storing.
Delete
ADDR_MEMORY_CLEAR: Deletes the local memory contents. All address data changes made since the first call of any function module, or the last local memory save, are discarded. This module should be called after extensive read operations or when returning to the application.
Number assignment:
When assigning numbers to addresses or persons, their (first) use must be specified.
ADDR_NUMBER_GET
Assigns an address number, i.e. converts a temporary address number (address handle) into a permanent address number which is saved in the database key.
ADDR_PERSON_NUMBER_GET
Assigns a person number, i.e. converts a temporary person number (person handle) into a permanent person number which is saved in the database key.
Where used:
A permanent address or person number must have been assigned before a (further) use can be entered.
ADDR_REFERENCE_INSERT
Inserts a new use in an existing address.
ADDR_REFERENCE_DELETE
Deletes a use of an existing address.
ADDR_PERSON_REFERENCE_INSERT
Enters another use for an existing person.
ADDR_PERSON_REFERENCE_DELETE
Deletes a use for an existing person.
Applications are also deleted by the normal delete operations when the application passed to the delete modules is not the only one, or most recent one.
Address object methods
Read:
Read address objects
<Address object>_GET: Reads a (fully qualified) address. All versions of this address are read into local memory, and are subsequently accessible without database access.
ADDR_PERSONAL_GET_ALL: Reads all private addresses for a person. All versions of this person's private address are read into local memory, and are subsequently accessible without database access.
Read address object block
<Address object>_GET_ARRAY: Reads several (fully qualified) addresses. The database and the local memory are read. All address versions read are subsequently in local memory and can be accessed without database access.
Insert:
<Address object>_INSERT
Inserts an address.
<Address object>_VERSION_INSERT
Inserts a version of an address.
ADDR_PERSONAL_COMPLETE_INSERT
Inserts a private address with full specification of personal and address data, in contrast to ADDR_PERSONAL_INSERT, where the person data already exist.
ADDR_PERS_COMP_ASSIGN
Assigns a company address to an existing person, in contrast to ADDR_PERS_COMP_INSERT, where the person is also newly entered.
Change:
<Address object>_UPDATE
Changes an address version. (In particular the standard version, "the" address, is changed.)
Delete:
<Address object>_DELETE
Deletes an address. All existing address versions are deleted.
<Address object>_VERSION_DELETE
Deletes one version of an address.
Search:
<Address object>_SEARCH
Searches for addresses, which can be partially qualified (e.g. by attribute value specification). Only the database contents are searched (the local memory should be saved first, under certain circumstances).
Communication addresses
Read:
<Address object>_COMM_GET
Reads the communication addresses of an address object for a particular communication type. All communications addresses of the specified communication type, for the specified address object are read into local memory, from where they can subsequently accessed without database access.
Maintain:
<Address object>_COMM_MAINTAIN
Maintains the communications addresses of an address object for a particular communications type. Maintenance comprises: create, change and delete. All communications addresses thus maintained can be accessed in local memory without database access.
III. Maintenance with dialog
Function groups SZA1, SZA5, SZA6, SZA7 and the parameter transactions SADR and SADP
--> Overview in the SZA1, SZA5 and SZA7 function group documentation.
IV. Application examples
0. General
    - The function group does not need explicit initialization.
    - Address data changes are only written to the database after
      'ADDR_MEMORY_SAVE' has been called.
    - Before the 'ADDR_MEMORY_SAVE' call, all temporary
      address and person handles must be converted to external
      numbers.
1. Read access to normal address (address object 1)
Selection parameter for a normal address
    data: begin of selection
            include structure addr1_sel.
    data: end of selection.
Attributes of a normal address
    data: begin of result.
            include structure addr1_val.
    data: end of result.
Specify selection parameters
    clear selection. "no handle, default nation, today
    selection-addrnumber = t001-adrnr.
Read normal address
    call function 'ADDR_GET'
         exporting address_selection = selection
         importing address_value     = result
         exceptions address_not_exist = 1
                     parameter_error   = 2
                     version_not_exist = 3
                     internal_error    = 4.
    case sy-subrc.
    endcase.
Result output
    write: / result-name1,
           / result-street, result-house_num1,
           / result-post_code1, result-city1.
Delete local memory after end of processing
    call function 'ADDR_MEMORY_CLEAR'
         exceptions unsaved_data_exist = 1
                      internal_error     = 2.
    case sy-subrc.
    endcase.
2. Search for a normal address (address object 1)
Search parameters for a normal address
    data: begin of selection
            include structure addr1_find.
    data: end of selection.
Result table for a normal address search
    data: begin of result occurs 0.
            include structure addr1_val.
    data: end of result.
Address group table
    data: begin of dummy occurs 0.
            include structure adagroups.
    data: end of dummy.
Number of addresses found
    address_count like sy-tabix.
Specify search parameters
    clear selection.
    selection-name1 = 'SAP*'.
    selection-city1 = 'Walldorf'.
Search for normal address
    call function 'ADDR_SEARCH'
         exporting search_in_all_groups = 'X'
                      search_for            = selection
         importing addresses_found_count = address_count
         tables     search_result         = result
                      address_groups        = dummy
         exceptions parameter_error       = 1
                     internal_error        = 2.
    case sy-subrc.
    endcase.
Result output
    loop at result.
      write: / result-name1,
             / result-street, result-house_num1,
             / result-post_code1, result-city1.
    endloop.
3. Bulk processing of normal addresses (address object 1)
Table of selection parameters for a normal address
    data: begin of selection occurs 20.
            include structure addr1_sel.
    data: end of selection.
Table of attributes for a normal address
    data: begin of result. occurs 20.
            include structure addr1_val.
    data: end of result.
Error table
    data: begin of errors occurs 0.
            include structure addr_error.
    data: end of errors.
Specify selection parameters
    clear selection. "no handle, default nation, today
    selection-addrnumber = t001-adrnr.
    append selection.
    clear selection.
    selection-addrnumber = vbpa-adrnr.
    append selection.
    ... enter further selections in table selection ...
Read normal address in blocks
    call function 'ADDR_GET_ARRAY'
         tables     address_selection = selection
                     address_value     = result
                     error_table       = errors
         exceptions parameter_error   = 1
                      internal_error    = 2.
    case sy-subrc.
    endcase.
Result output
    loop at result.
      write: / result-name1,
             / result-street, result-house_num1,
             / result-post_code1, result-city1.
    endloop.
Delete local memory after end of processing
    call function 'ADDR_MEMORY_CLEAR'
         exceptions unsaved_data_exist = 1
                      internal_error     = 2.
    case sy-subrc.
    endcase.
4. Create a normal address (address object 1)
Address number, address handle, address group, address data
    data: address_number like adrc-addrnumber.
    data: address_handle like szad_field-handle.
    data: address_group like addr_ref-addr_group value 'DEBI'.
    data: begin of address_data.
            include structure addr1_data.
    data: end of address_data.
Use details
    data: begin of usage.
            include structure addr_ref.
    data: end of usage.
Error table
    data: begin of errors occurs 0.
            include structure addr_error.
    data: end of errors.
Return codes
    data: rc_insert like szad_field-returncode.
    data: rc_number_get like inri-returncode.
    data: rc_memory_save like sy-subrc.
    data: lv_check_address like szad_field-flag.
Fill address record and determine temporary address identifier
    address_data   = ...
    address_handle = ...
Deactivate address check if required
    lv_check_address =
Insert address in local memory
    call function 'ADDR_INSERT'
         exporting address_data    = address_data
                     address_group   = address_group
                     address_handle = address_handle
                     check_address   = lv_check_address
         importing address_data    = address_data
                     returncode      = rc_insert
         tables     error_table     = errors
         exceptions address_exists = 1
                     parameter_error = 2
                     internal_error = 3.
    case sy-subrc.
      when 0.
        if rc_insert = 'E'.
          Analyze error_table and call special further processing
          because the address has errors and was not created.
            endif.
    endcase.
    ... process other application objects
        or modify Business Address Services
        local memory ...
    ... before saving potential application objects:
Declare final use to address management
    usage-appl_table = ...
    usage-appl_field = ...
    usage-appl_key   = ...
    usage-addr_group = address_group.
Assign address number
    call function 'ADDR_NUMBER_GET'
         exporting address_handle           = address_handle
                      address_reference        = usage
         importing address_number           = address_number
                      returncode_numberrange   = rc_number_get
         exceptions address_handle_not_exist = 1
                      internal_error           = 2
                     parameter_error          = 3.
    case sy-subrc.
    endcase.
    ... immediately afterwards:
save local memory after processing
    call function 'ADDR_MEMORY_SAVE'
         exceptions address_number_missing = 1
                     person_number_missing   = 2
                     internal_error          = 3
                     database_error          = 4
                     reference_missing       = 5.
    case sy-subrc.
    endcase.
delete local memory
    call function 'ADDR_MEMORY_CLEAR'
         exceptions unsaved_data_exist = 1
                      internal_error     = 2.
    case sy-subrc.
    endcase.
V. Terms/Glossary
Address/Person group
Addresses and persons can be assigned to an address or person group. One address or person can be assigned to several groups (multiple assignment). This allows e.g. the same address to occur as customer and supplier address, and also allows searches to be limited to certain groups, instead of always searching all addresses.
Logical groups of addresses and persons can be formed.
The address groups required by applications are established by the application developer in consultation with the SAP Business Address Services. Customers can define their own groups in the customer name range for their own developments.
Address/Person handle
Address data are saved in the database and address and person numbers are assigned only when the application data are saved. Application programs must call the appropriate function modules. Business Address Services hold the data in internal tables in the local memory of the function group SZA0. Before saving after creation, addresses or persons are identified by an address or person handle, via which address objects can be accessed until the data are saved in the database.
The handle of a person, a normal address or a person in a company is determined by the application program.
The following procedure is recommended for both the address and person handles:
The first 10 places contain the name of the table in which the address or person is referred to. The next 10 places are used for the name of the field containing the reference, and the application data set key can be written in the remaining 120 places. This can be a temporary key, as the database key is only completed when saving in many application areas.
In this way the application developer can manage the addresses with the data which he or she is accessing anyway.
Ambiguities are avoided in complex transactions in which addresses for different applications are kept simultaneously in the same roll area for SZA0 (a serial number may not be sufficient as a handle).
Communication addresses
A communication addresse in the central address management is the identification number or address of a communication connection of one of the following communication types: telephone, fax, teletex, telex, SMTP, R/Mail, X.400 or RFC.
e.g. the complete telephone number (dialling code + telephone number) is the identification of the communication address of type telephone.
Address/Person number range
The address and person number range defines the valid external identifications (database key value range) for addresses or persons. For reasons of compatibility, the same number range applies as for 'old' SADR and SADRP addresses. Specifically, address and person numbers are drawn from the same number range. This simplifies the conversion of old SADRF and SADRP addresses.
Address versions
The (international) version of an address is an independent address object data set, in which a different display style of an address can be maintained in a code page (e.g. in Japan in Kanji, Katakana or Hiragana).
These are not independent addresses
The part of the address object which does not depend on the display style is always in the standard version.
In customizing (transaction SADV or under Cross-application components -> General application functions -> Address management -> Maintain address version display formats) you can set which other versions, in addition to the normal display style, are to be offered for maintenance.
Where-used list
In the where-used list, the application objects in which an address or a person are referred to is recorded. The where-used list is a technical support for the repeated use of addresses or persons in the three address types and therefore refers to the (sub)object address and person.
Immediately before calling the function module 'ADDR_MEMORY_SAVE', the function modules 'ADDR_NUMBER_GET', or 'ADDR_PERSON_NUMBER_GET' must be called once for every normal address and once for each person (for private addresses and addresses of a person in a company). The (permanent) use of the address or the person in the application must be specified. In exchange the calling program gets the assigned numbers of the addresses and persons for the references in the application data records.
Then (still before the 'ADDR_MEMORY_SAVE' call), other uses of addresss or persons can be specified via the function modules 'ADDR_REFERENCE_INSERT' or 'ADDR_PERSON_REFERENCE_INSERT' for multiple use.
This is always possible once the address or person number is assigned.
At the end of processing, the data must be saved in the database (as for all other address data) with the function module 'ADDR_MEMORY_SAVE'.
Thanks,
Sree.Manam
Edited by: manam narayana on Jun 18, 2008 9:00 AM

Which table contains - Customer Master Changes?

Team,
Which table contains - Customer Master Changes?
Please be specific; For example:
CDHDR:
OBJECTCLAS ?
CDPOS:
BJECTCLAS?
ABNAME
ABKEY
HNGIND
Thanks

Hi Naved,
try this:
CDHDR-OBJECTCLAS = 'DEBI'
CDHDR-OBJECTID = customer no.
CDPOS-OBJECTCLAS = 'DEBI'
CDPOS-OBJECTID = customer no.
CDPOS-CHANGENR = CDHDR-CHANGENR
CDPOS-TABNAME = 'KNA1'
CDPOS-TABKEY = sy-mandt + customer no. (key of table KNA1)
CDPOS-FNAME = field modified
CDPOS-CHNGIND = (U Update, I Insert, D Delete)
Regards, Manuel
PS: Please remember to reward points if the answer is useful.

Output proposed from customer master

Hello SDN!
I could not find output info in customer master.
Can I check with you if output can be proposed from the customer master when creating a sales order?
Or the only way output is determined is from output determination procedure where customer code can be one of the key condition record fields?
regards
Ravi

Hi,
Please go through the below Configuration process for Outputs
Output is a form of media from a business to one of its business partners. Ex: Printouts, Faxes, Telexes, E u2013 mails and Electronic Data Interchange (EDI). The Output determination component offers output functions for Sales, Shipping and Billing to help in manage sales transactions with our customers and within the organization.
Output can be sent to any of the partners defined in the document.
Outputs are usually in the form of order confirmations, delivery notes, invoices and shipping notifications.The output determination component offers output functions for sales, shipping transportation and billing to help in manage sales transactions with our customers and with in the organization.
We can create output.We can group output.Employers can send/receive output.
Output directly linked to the corresponding sales transaction Ex: Trough EDI.
System automatically proposes output for a sales and distribution document.
System uses condition technique to determine output.
We use output type to control how the output should be transmitted.
Ex: Via EDI, be printed.
We can determine output for all kinds of objects in SAP u2013 SD. Ex: For sales activities sales documents delivery documents and billing documents.
We can determine output, we can process output, and we can send output.
SAP uses condition technique to determine output.Output types can be Inquiry, Quotation, Order confirmation, Shipping document, Billing document, etc.The output can be sent through transmission mediums.
Ex: Local printer, Fax, Telex, E u2013 mail, SAP inbox or even to SAP.
Output determination closely integrated with technical module as technical consultant prepares the output format in SAP script or smart forms.
Configuration settings:
Output determination for sales documents: Transaction code: V/57
Path:
 IMG
 Sales and distribution
 Basic functions
 Output control
 Output determination
 Output determination using the condition technique
 Maintain output determination for sales documents
 Maintain condition tables
 Maintain output condition table for sales documents
Save and Exit
Maintain output types: Transaction code: V/30
We define output types for output type records. Out put type represents different output.
Ex: Quotation, Order confirmation, etc.
Path:
 IMG
 Sales and distribution
 Basic functions
 Output control
 Output determination
 Output determination using the condition technique
 Maintain output determination for sales documents
 Maintain output types
 Check different output types existed or not
Ex: AF00 = Inquiry
AN00 = Quotation
BA00 = Order confirmation
LP00 = Scheduling agreement
MAIL = Internal message
RD03 = Cash sales invoice
 Click on change/display icon
 Choose u201CBA00u201D
 Click on copy icon (press ENTER till 28 entries copied) and rename it
 Select our output type
 Check u201CMail titleu201D and u201CTextu201D control button whether mail and texts are existed in all languages or not
 Check processing routines for all transmission mediums are existed or not
 u201CProgramu201D, u201CFORM routineu201D, u201CFormu201D are maintained and provided by technical consultants.
 Check partner functions has been assigned to transmission mediums in partner functions control button
 Save (press ENTER up to u201CSAVEu201D request disappears)
 Come back
 Go to details icon
 Assign access sequence [ ] (create access sequence in next step)
 In general data section
Check access to conditions
 In default values section
Maintain dispatch time as u201Csend immediatelyu201D
Transmission medium: u201CPrint outu201D
Partner function: SP
 In time section
Check timing: 1
 Save and Exit
Maintain access sequence
Path:
 IMG
 Sales and distribution
 Basic functions
 Output control
 Output determination
 Output determination using the condition technique
 Maintain output determination
 For sales documents
 Maintain access sequences
 Go to new entries
 Define your access sequence
 Select it and click on accesses icon
 Go to new entries
 Specify access sequence No. 10
Table No. Ex: 001
 Save and Exit
Assign output types to partner functions
Path:
 IMG
 Sales and distribution
 Basic functions
 Output control
 Output Determination
 Output determination using the condition technique
 Maintain output determination for sales documents
 Assign output types to partner functions
 Check whether the system has copied output types with relevant transmission mediums and partner functions
 Save and Exit
Maintain output determination
Path:
 IMG
 Sales and distribution
 Basic functions
 Output control
 Output determination
 Output determination using the condition technique
 Maintain output determination for sales documents
 Maintain output determination procedure
 Choose standard output determination procedure u201CV10000u201D
 Copy and rename it
 Save and select our output determination procedure
 Click on control data button and change output type u201CBA00u201D as ours Ex: SREE
 Save and Exit
Assign output determination procedure
Allocate Sales Document Header: Transaction code: V/43
Path:
 IMG
 Sales and Distribution
 Basic functions
 Output control
 Output determination
 Output determination using the condition technique
 Maintain output determination for sales documents
 Assign output determination procedure
 Assign Sales Document Header
 Choose sales document type u201CORu201D from position button
 Assign out output determination procedure (ours) Ex: SREE
 Save and Exit
Sales Document Item: Transaction code: V/69
Path:
 IMG
 Sales and Distribution
 Basic functions
 Output control
 Output determination
 Output determination using the condition technique
 Maintain output determination for sales documents
 Assign output determination procedure
 Assign Sales Document Items
 Choose item category as u201CTANu201D form position button
 Assign our output determination procedure
 Save and Exit
Maintain condition record: Transaction code: VV11
Path:
 Logistics
 Sales and distribution
 Master data
 Output
 Sales document
 VV11 u2013 Create
 Specify our output type Ex: SREE
 Click on key combination
 Maintain the details like below
Customer No. Partner
function
Message transmission medium
[M]
Dispatch date Language
1001007 SP 1 18 u2013 02 u2013 06 EN
 Select condition line item
 Click on communication
 Specify outputs devise [LP01]
 Check print immediately
 Save and Exit
 Go to VA01 and raise the sales order
 Go to Extras  Output  Edit  Check condition record values are copied or not
 Save and Exit
 Go to VA02  Extras  Output  Header  Print preview
 Check the result
Steps:
1. Put the fields into the field catalog that you will need.
2. Create the condition tables.
3. Create the access sequence
4. Assign the condition tables to the access sequence
5. Create the condition types
6. Assign the access sequence to the condition type
7. Create the determination procedure (if necessary) and assign the condition types to it.
8. Assign the determination procedure.
9. Create your condition records.
Regards,
Siva

Changes in customer master data

Hi
Is there a different way (apart from using IDOCS) to identify changes (create/update/delete) in customer's master data to the following Condition Class:
BPAR
TESTRF
DEBI
KLIM
Best Regards
Tal

Hi
I want to know if all the changes in customer master data objects: BPAR,TESTRF,DEBI,KLIM
are recorded in the system and where?
is it relevant to customization?
Best Regards
Tal

Why customer master idoc named like DEBMAS?

hi,
i am just curious know why customer master idoc named like DEBMAS?
vendor master data idoc as cremas?
any German abbreviation or English abbreviation behind this will be appreciated.
thanks & regards
Raja
Message was edited by:
Raja

To my knowledge I do not think that the naming has anything to do with the German translations since in German:
Customer = Kunde and
Vendor = Verkäufer....
However the naming has some connection with the Business Case behind customers and vendors. In SAP, a customer is a business partner whose account you debit for money, hence the name DEBMAS and a vendor is a business partner whose account you credit money, hence the name CREMAS.
PS: Reward points and close the question if you find this helpful.
Regards.

Customer Master data.. Bank Account No.

Hi
In customer master data ( XD01) > General Data > Payment Transaction > Bank Details
we maintain. Bank key , Bank Account and other details.
my concern is , by maintaining customer bank account number in customer master data, what are the integrated effects to FI > Bank Accounting > House Bank ? ( On Invoice Creation, Payment Receipt , Credit note, Debit note all FI Transaction ).
Actually we want to use it just for information & reporting purpose. NOT FOR ANY AUTOMATIC RECEIPT \ Integration to FI > BANK Accounting \ House Bank.
Thanks

Hi.
'customer master data, what are the integrated effects to FI > Bank Accounting > House Bank ?' House bank not linked with Customer master data(only if customer affiliated company).
Bank details in customer could be used eg for invoicing(printing form)

Contact Role in Customer Master

I have assigned following roles to the 'Customer Contact' in Customer Master. Could someone help me what all the notifications customer contact will get from OM/any other module if he has this role assigned? Or does it depend on how OM implementation/customization client has?
Contact Role = Shipping Notification
I also wondered about Contact Role = Acknowledgement. I found few customizations to send 'SOA' and 'Delay shipment' emails to contact with this role. I wonder what are the standard email notifications will be sent by Oracle.
Thanks

Hi,
As part of standard functionality, based on the contact role I don't think any notification will be triggered, it depends on the customizations.
Regards,
Sridhar

Customer master table

Can u please tell me customer master line item table & is their any specific like debit line item table and credit line item table available in sap. please give me explanation above this question

Hello,
Please refer this document.
http://www.abap.es/Descargas/TAB%20-%20Relacion%20de%20las%20tablas%20por%20modulos.PDF
There is no debit line item table and credit line item table.
Following are the customer and accounting document related tables.
BKPF - Accounting Document Header
BSEG - Accounting Document Line item
BSAD - Secondary Index for Customers (Cleared items)
BSID - Secondary Index for Customers (Open items)
Customer master data is stored in KNA1 and KNB1
Regards,
Ravi
Edited by: Ravi Sankar Venna on Apr 8, 2009 12:13 PM

Customer Master - Debit Notification Preferences

Similar Messages

Maybe you are looking for