Regarding customer master delivery agreements

hello gurus,
in customer master shipping tab,we have customer delivery agreements like complete delivery and partial delivery fields.
and we have different options in partial deliveries.
can any body explain me what is the use of different options in partial deliveries with situations.in which situations the customer will go for different partial delivery options.
i have understood the functionality of these options but what i need is the situations at which customer will go for these agreements.
thanks in advance,
kishore

Hi,
Complete delivery is one where a complete delivery has to be made to the customer and no partial deliveries allowed. For example, assume a chemical or pharma product made of batches. In this case customer may need complete deliveries, in batches and the batches can't be splitted in deliveries. For example, batch xyz quantities should be sent be sent in only one delivery and can't be sent in multiple deliveries. The reason could be, chemical components may have variations that may be further affected by outside temperture etc., the customer may like to get the delivery (batch quantity) as complete delivery only.
Some customers may accept partial deliveries, if the complete quantities are not delivered. For example, instead of waiting for complete delivery, if partial deliveries are available, the customer's processes need not get affected. Hence using this field options a vendor can discuss with customer about the possible delivery options when they sign contracts.
Regards

Similar Messages

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

Customer master creation and maintenance

Hi All,
I have a question regarding customer master. The client is implementing FSCM credit and collections management. Initially, all the existing customers in AR are mapped or loaded to SAP Business partner using the functions available (I dont remenber on top of my head but i know we can do that).
Now my questions are,
1. When creating a new customer later some point, do we have to create in AR and then establish the relationship to SAP Business partner. Or directly create as SAP Business partner.
2. If to be cretaed both in AR and as Business partner, this would be kind of duplication or maintaing in 2 seperate places. Please explain the reason behind it.
3. If only to be created as Business partner, will all the fields available in Customer master (like business area, accounting clerk, Industry field) be available in Business partner
one more question, We can automatically import credit data from External Credit Information service. Can we push the data from our system to the Provider like the payment data or anything for that matter. Client has a requirement for this to send data to provider and I am not sure. Please confirm.
I know there are too many question, but please help me undertsand this more better.
Regards,
Satya

I am sorry about that but first 3 questions are related and linked.
I understand that a link is established between AR customer data and BP's and this will migrate all data. But the data will be in AR and will be copied to BP..right.
Likewise, if you create a customer in AR, it will create a BP...will this be done automatically?
And later if we want to create a new customer, do we need to do in AR and this will automaticall create a BP? Is this not duplication. I know that BP are maintained centarlly and for master data synchronization.
Regards,
Satya

How to Flag Customers in Customer Master (in SD)

Hi,
I've read a few earlier posts regarding customer master and since I could not find an answer for my query I am posting it here.
I have a question regarding the customer master in SD: Is there a way to Flag Customers for reporting purposes in Customer Master for SAP SD.
Is there some standard funtionality in SAP to do so ?
We have a few customers that belog to the US governmnet and due to government regulations if we do certain amount of busniess with them or gov agencies or government contractors we need to send the gov a formal report.
So for this reason we need to flag customers so we can run reports and see how much is being done.
I wanted to know if there are some other users/ companies that are doing this and if so how are they handlling such situations?
I would appreciate if some one could help me with this as this is knid of an urgent requirement.
Thanks in advance.
Neha

Hi,
SAP has given some standard report based on those reports you can see the sales values for customer,material,based on sales orders and billing document etc.. like this.
but if you want to see theese reports frist you have to configure this (LIS Logistics Information System)
Path:SPRO>Logistics-General>Logistics information system>Logistics data warehouse>Updating>Updating control>Settings:Sales, here you have to set in statistic group,update group settings.
Againe here defined statistic groups are assigned in customer master fro the field statistic group in sales area data>sales tab.
Likewise you can also activate based on material and sales documents in above specified path.
Thank you,

Customer Master,for a Vendor, takes wrong Ship-to in Return Delivery

Hi Everyone,
Process: Return to vendor based on the standard PO (type NB) with return delivery (type RL).
Settings Made: A customer master with account group Sold-to created and the code maintained in vendor master and vice versa. In this customer master Ship-to parter is not the same as other partner functions. Say Sold-to = Billed-to = Payer = 1234, but Ship-to = 5678.
Issue: Whenever a return delivery is created agianst a PO (in VL10D) the system proposes Ship-to customer same as the sold-to 1234 . Delivery is getting processed without any error but the question is why system should propose 1234 as Ship-to which is not defined in the parter functions of Sold-to cusotmer 1234? Instead system should take 5678 as Ship-to which is the only entry in the sold-to cusotmer 1234 available.
If a sales order is created for this customer, system correctly populates Sold-to (1234) and Ship-to (5678). The issue is only when a return delivery gets created against a standard PO.
Kindly advise.
Thanks,
Hemant

Hi
My reply to you is more of logical than SAP
Normally SP is the most dominant and important party in a sales process
If you have a different SH in a CMR that means this sold to party tells you rather than delivering goods to me you deliver it to this person
In standard SAP goods receiving hrs,Taxes,ship to address these are the data taken from a SH in a sales order
In case of returns the decision to return stocks will be taken only by SP and not the person who receives the goods
What i am telling is more of logical business process
That is why the system is proposing likewise
May be the other experts has give better explanation for this
Regards
Raja

Text from customer master to delivery header

Hi Experts,
Here we have a requirement, Text what we maintain in the customer master (like Shipping point address) text need to be trigger at Delivery header,
1) Is it possible in standard text determinaction or we need to go for any user exits?
2) If we want to use user exits what are the user exits we have to copy the data from customer master to delivery header.
NOTE: Client doesnt want to use the text from sales order or scheduling agrements.
Please help me to fill the requirement .
best regards,
chiranjeevi

Hi Chiranjeevi,
It is possible to achieve this with standard text determination procedure itself.
Goto transaction VOTXN and in the "Delivery --> Header" create a new access sequence with the Customer Master Text IDs (like the ID which contains the Shipping Point address) from which the text is to be selected. Once done, create or make use of an existing text determination procedure available under Delivery Header and then assign the access sequence to the Delivery Header Text ID into which the Customer Master text is to be copied. Maintain additional settings as necessary. This will ensure that the text from customer master is directly copied over to the delivery header.
There are many documents already available (search in Google) to explain the text determination process if you need help with the same.
Regards,
Som

Return to vendor via delivery customer master

Hi Gurus,
I am doing the return delivery to vendor(122) via delivery.
Now when I am creating the vendor and selceting Returns vendor and shipping
condition sytem (and account group for customer) is creating a customer master in
the background.
Now when I am seeing the customer master XD03 it is created with general data and
Sales Org data.no comapany code data is created.
And I can find that this customer is created for
Sales Org 1000
Dist. Chn 10/12/00
Now my question is why only this 3 combination is created and how it is determined
or where we maintain this in customization.
Thanking you

Hi,
Thanks for your valuable input.
But I find that My POrg 1000 is assigned to 10 plants ( other than my plant 1000)) in T024w
and at the customizing -> Assignment Sales Organization/Distribution Channel - Plant (table TVKWZ)
and My plant 1000 is assigned to at least 50 combination of S.org and D.ch (TVKWZ)
Just curious why out of so many combination system is creating only 3
Thanks in advance

Details regarding Create customer master record

Hi,
Can anyone gv info regarding Creating customer master record.
I need Existing Bapi's for the same.
Thanks in advance.
Purna

Check out the bapi:BAPI_CUSTOMER_CREATEFROMDATA1.
To know of how to use it, check its documentation, it is very well documented.
hi karthik, shaik can not reward points as he did not mark this as a question.
Regards
Gopi

Pulling Over/Under delivery Tolerances from Customer Master into CMIR

Is it possible to pull the over/under delivery tolerance values from the customer master info the CMIR? I don't understand why the delivery priority flows from the cusotmer master to the CMIR but the Over/Under Tolerances do not. I've looked at SAPMV10A ... it looks like I might be able to use an enhancement spot to add the necessary logic but I've not used this type of user exit and I'm not sure if there is a better solution (like some configuration that I'm missing ???) Any advice would be appreciated. Thanks!

Hi Mallisa,
I tried creating a CMIR record and both Delivery Priority and Over/Under Delivery tolerance were copied in CMIR record from Customer Master.
BR,
Anshul Chohan

Regarding Text in Customer Master

Dear All,
How does text maintained in the customer master gets copied in the sales document.What are the configuration settings one shoul maintain for the same.
Regards
Atul

In VOTXN you have to do the following
- Text object customer, press bullet Sales & Distribution
- Press button text types.
- You see that you can create a text ID for object KNVV, create one.
- Go back and press button change, you are now in the text det. procedure for customer
- If there is no procedure, create one.
- You have to assign your procedure to a group (eg. sold to party, ship to etc.)
- Now you have to go into the text id's in the textprocedure and add your newly created object
- When you brach to your customer, you will see your object.
- In VOTXN again, you have to create also a text determination for your sales document.
- You have to create a new text id for what you want to see in your sales document, so follow the steps like for the customer master, but now you make a text object of type VBBK
- Next, you have to branch to the bullet sales and distribution header - change.
- If there is no text determination available, you have to create a text procedure and add the text id with VBBK in this procedure.
- Now to determine that you have to copy the text from the customer master to the sales document header, you need to create an access sequence. Make one and branch to accesssequence for text id's.
- Add in this acces sequence your newly created text ID (type KNVV)
- Go back to the text ID's in Textprocedure and add the accessequence for your ID.
- You can influence your behaviour (mandatory or that a popup is shown during sales order entering)
- Last thing assign your created procedure to the sales document type you want this to work for.
Hope this helps.

Regarding ALE-iDoc for Customer Master, J1ID and FD32

Hello all
Scenario:
As per client's requirement we have to develop idoc so that followings requirements will meet:
Say there are two servers a) MDM Server b) PRD Server
1] As and when I'll create customer master data in MDM server then customer master should get created with that data in PRD server
which I can achieve through BD12 by doing some idoc enhancements
2] Simillarly when i'll create data using transaction J1ID and FD32 in MDM Server (Data relevant to customer master) then that data also should get created in PRD server using Idoc
May I know which
1)message type we can use (as we use DEBMAS in case of Customer Master) for J1ID and FD32
2) Any transaction to send data from one server to another server for transaction J1ID and FD32 (as we use BD12 in case of Customer master for sending data created using transaction XD01)
Thanks,
Mahesh

Hello Mahesh,
In the case of customer master it would be better if you would use standard message types and t code to transfer ddata.
But in the case J1ID and FD32 you can build a standalone idoc
Follow these steps to build custom message types and futher transactions
WE81 - Create message type
WE31 - Create segment
WE30 - Create Idoc type
SALE - Define Logical system (not required if already exists)
SM59 - Define RFC (not required if already exists)
WE21 - Define ports (both in sender and receiver)
WE20 - Define Partner profile (both in sender and receiver)
BD46 - Distribue the model view.
SE38 - Create a program to send the idoc in the sender sytem.
SE37 - Build inbound function module to receive the idoc for receiver system
WE57 - Assign FM to message type
BD51 - to change the characteristics for inbound FM
WE42 - Create Inbound process code.
Hope this would help you.
Thanks and Regards,
Ranjith Nambiar

Regarding segments in GL master, Vendor master, customer master

Hi
friends
can any one tell me how many segments in GL master, Vendor master, Customer master.. I give your points...
Thank you
[email protected]

Hi Kumar
in GL - Chart of accounts level and company code level
in Customer - Sales org level and company code level
in Vendor - Purchase org level and company code level
Thanks
Ashok
Assign points for useful answer

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

Confirmation of sensitive filed of customer master

Hi all
Is that possible to BLOCK or NOT TO CREATE a sales order, if confirmation of sensitive filed of customer master yet to confirm ?
Is that need user exit or can we do Configuration.
Need your suggestions.
Regards,
Nagesh

Hi Nagesh,
behaviour of Sensitive filed is once activate some fields as a sensitive filed's if user change that field data from the master record system will stop payments until confirm the changes from other user.
But system not stop Sale order / Delivery / Invoice creation even though fields data change from master system will stop only payments for perticular customer / vendor.
The other name for sensitive filed is dual control. once fileds activated it will applicable entire client not to comp code.
Regards,
Viswa

Deleting a Contact on Customer Master with that Contact on Open Sale Orders

Our current SAP system ECC 6.0 allows a user to delete a Contact from the Customer Master where that Contact is also on Open Sales Orders.
Then when our create delivery job runs, it abends saying Contact record not found.
How is this normally handled ? Are users not suppose to delete Contacts from the Customer Master if they are attached to an Sales Order ? Is there some config to turn on in SAP that checks for Open Sales Orders before deleting a Contact in the Customer Master ? Do I code this check in User Exit on the Save in the Customer Master and not let user delete the Contact if it's attached to Open Sales orders ?
Would appreciate any help on this.
Thanks,
David

Hi David,
Try this user exit.
RFDRRANZ User exits: Accounts Receivable Information System
Regards,
Vijay

Regarding customer master delivery agreements

Similar Messages

Maybe you are looking for