Central contract distribution trough IDOC - including new partner

Hi,
I created a partner in SRM for use with a specific central contract that I am distributing the ECC through an IDOC, the contract in backend is configured with this partner as mandatory, but if I process manually the data in the IDOC in ECC, document is not created, message error is that new partner missing.
Any ideas how can I add a partner in this process?
I'm working with SRM 7.0 and ECC 6.0
Regards,
José Luis D.

To trace where your issue might be, it is helpful to find out the following:
1) in table BBP_BACKEND_DEST, get the SYS_TYPE value for your backend system (LOGSYS = your backend system)
2) in table BBP_FUNCTION_MAP, get the function name for OBJECT = BUS2000113 and METHOD = TransferFromData and TYPE = <your value from step 1>
If you are going through IDOC processing, likely the Function would be "B46B_CTR_TRANSFER". In that case, set a session breakpoint in that function module. Then test run FM BBP_PD_CTR_TRANSFER with your contract GUID as input parameter and IV_SAVE_DB = "X". Execute until the breakpoint and start tracing the problem. This should help you identify the source of the error.

Similar Messages

SRM 7.0 Central Contract- Distribution to backend failure

Hello experts,
We are implementing SRM 7.0 Central contracts scenario with PI.
The Contracts get created and Released but the problem is that the Distribution to backend fails. The Status in BBP_PD shows 'Distribution Incorrect' and the RZ20 gives an error 'Backend data cannot be read'.
We checked all the configuration settings (including the PI settings) and everything seems to be in order.
Would appreciate if someone could throw some light on the potential cause of the problem.
Thanks
Raman.

Message must have created . check all SRM outbound transactions .but PI could not catch them.
Note 1284369 - User attributes check in Contract distribution via services - what is your SP level in SRM 700.
The sap stratergy in earlier version
table in ECC BBPD_CTR_IDOCREF with message 019-This will result in setting the GOA status to 'Distribution Incorrect'.
so SAP might have tried the same way in CCTR as well, Once message are created and this message number like IDOC number updated in ECC table for the further refrence .so like wise SRM trying to communicate the same to ECC but it would have failed.
do you remeber when GOA idoc fails this table we will have reference number and reprocessing idoc.
like any reference of your input must register in one ECC table but there may have this table or some other reference table.
/SAPSRM/CL_CH_SOA_MAP_CTR_OUT CLASS DO SOME trick and see what is happening here
Muthu

Central Contract Distribution - line items creates many contract in the BE

Hi SRM Gurus,
We are in SRM 7 ECC 6 Ehp 4 PPS. Ext Classic.
First of all, CCTR - Central Contract can't be distributed as per SAP for PPS impl.
But we have a workaround.
We made snote 1354971 read with 1423994 implemented. Made the process work.
Means Assign distribution on the item level was enabled and Distribution reached BE.
But when we have multiple line items in the Central Contract, and we assign distribution, it creates one contract per line item in the Backend which is really absurd. Which means if you have 100 line items, its creating 100 contracts. When we do the call-off against this central contract, we have multiple contracts.
Gurus, Can you guys throw some light on this entire issue.
with regards,
Freemind

We are having nearly exactly your scenario and CCTR works fine with 1 distributed contract containing multiple items. Check if all the items are distributed to the same purchasing org and location. If all is the same, debug BBP_PD_CTR_TRANSFER with your SRM contract GUID to see when and how multiple contracts get created in ECC.

Central contract distribution in PPS

Hi All,
With reference to this forum link, it is possible to distribute central contracts in PPS to ECC.
http://forums.sdn.sap.com/thread.jspa?threadID=1915922
I want to enable the assign distribution button. Pls help me with entries what to maintain in this table.
/SAPSRM/V_MDA_HC
Thanks and Regards,
Abdul Raheem

closing thread

Central contract distribution in two backend ERP system

Hello All,
I am implementing SRM 7.0 Contract management (SAPKIBKV07) with two backend ERP system.
We have a requirement where we will create a Global contract in SRM system. Upon distribution based on purchase organisation this contract should get distributed to two different backend system.
Q-1) Is this a standard featutre available with Contract management or de we need set up some configuration. If yes, then please let me know the details.
Q-2) Again here the master data for both the backend system is not synchronised hence if a Global contract in created in SRM system and distributed to two different countries then each contract in ERP should have the region specific vendor code ?
How this functionality can be achieved.
Thanks,
Yatin

Hello All,
Has anyone implemented contract management with two different backend system and with different master data set up
Thanks,
Yatin

SRM 7.0 EhP 1 central contracts with service lines

Hi,
I have a question concerning the use of SRM 7.0 EhP1 central contracts with service line items. I know that for SRM EhP 1 you would require EhP 5 in ECC. However, since my organisation just went to EhP 4 last weekend I am wondering if there's any option to use services in central contracts without going to EhP 5 in ECC.
Kind regards,
Bastiaan

Hi Laurent,
Yes.
When Central contract was designed in SRM 7.0 with ERP EhP4, it was designed with no service hierarchy. But in SRM 7.01 Central contral was enhanced to handle service hierarchy and it works with ERP EhP5. The problem is when we have SRM 7.01 and ERP EhP4. To handle this complication SRM 7.01 was designed to send flat service lines to EhP4 and lower release even though Central contract in SRM has service hierarchy. So while transfering to ERP EhP4 system in standard, all outlines are not consider for transfer and only service lines (Functional items) are transferred to ERP. To do so user needs to maintain the backend destination information of the connected backend system in table BBP_BACKEND_DEST via SM30 transaction with correct system type (for EhP4 system it will be ERP_4.0 and for EhP5 ERP_5.0). SAP Standard program checks this while XML generation for transfer and if system type is ERP_4.0 system it removes all outlines from temp table before generating the XML data. When it is done, ERP has only service lines in its XML and it does the manupulation to create the replication of central contract.
Master Guide (Including Upgrade Information) - SAP SRM 7.01 states:
"The use of SAP NetWeaver PI is optional but it is required for outbound XML-based messaging or for connecting non-SAP planning or execution systems."
So service hierarchy is possible in SRM 7.01 and ECC 6.04 but only with PI. For other CCM functionalities, SRM 7.01 and ECC 6.04 without PI works fine.
Best regards,
Christian Zeuch

ERP release for Central Contract Management with SRM 7.0 EhP 1

Hi all,
i would like to have clarification with ERP and SRM release combinations regarding SRM 7.0 EhP1.
Indeed, the "Software Component Matrix for SAP SRM 7.0 EHP1", for Operational Contract Management, tells 'EHP 5 for SAP ERP 6.0 required'.
Moreover, in RKT dealing with SRM EhP1 delta overview, ERP 6.0 with EhP5 is mandatory for an upgrade to SRM7.01.
Nevertheless, i would like to have confirmation regarding this point.
We do not want to use PI to execute the Enterprise Services for CCM. So, we intend to switch BF SRM_WSRM_1 on.
But on the ERP side (EhP5), the only BF dealing with Contract Management is LOG_MM_P2PSE_2 which description is about Service Procurement (and more exactly for item hierarchies).
Does it mean we can use SRM 7.01 with ERP 6.0 EhP4 and without PI but only if we do not use Central Contracts with service hierarchies ?
Thank you for your help.
Regards.
Laurent.

Hi Laurent,
Yes.
When Central contract was designed in SRM 7.0 with ERP EhP4, it was designed with no service hierarchy. But in SRM 7.01 Central contral was enhanced to handle service hierarchy and it works with ERP EhP5. The problem is when we have SRM 7.01 and ERP EhP4. To handle this complication SRM 7.01 was designed to send flat service lines to EhP4 and lower release even though Central contract in SRM has service hierarchy. So while transfering to ERP EhP4 system in standard, all outlines are not consider for transfer and only service lines (Functional items) are transferred to ERP. To do so user needs to maintain the backend destination information of the connected backend system in table BBP_BACKEND_DEST via SM30 transaction with correct system type (for EhP4 system it will be ERP_4.0 and for EhP5 ERP_5.0). SAP Standard program checks this while XML generation for transfer and if system type is ERP_4.0 system it removes all outlines from temp table before generating the XML data. When it is done, ERP has only service lines in its XML and it does the manupulation to create the replication of central contract.
Master Guide (Including Upgrade Information) - SAP SRM 7.01 states:
"The use of SAP NetWeaver PI is optional but it is required for outbound XML-based messaging or for connecting non-SAP planning or execution systems."
So service hierarchy is possible in SRM 7.01 and ECC 6.04 but only with PI. For other CCM functionalities, SRM 7.01 and ECC 6.04 without PI works fine.
Best regards,
Christian Zeuch

Central contrcact distribution with WSRM with SRM 7.01 (EHP1)

Hi Gurus,
We are implementing Central contract distribution with SRM 7.01 and ECC 6 EHP 5 backends.
Can we use WSRM for Point-to-Point Communication for contract distribution? As the current customer does not have PI I am happy to avoid implementing PI.
Thanks in advance.

Hello Naveen,
Find the error details:
We have followed the steps for peer to peer service configuration as per note1268336 for synchronous service QUERYCODELIST for our XI independent scenario for contract management.
As per the steps for peer to peer for settings,we are done with the configuration in SRM side i.e. provider system and configured the QUERYCODELIST service.
Now while doing the same on ECC side(BDE) i.e. Consumer system when we are maintaining this service and creating Logical port,We get pop up to enter the details.
Once we enter the details and click on APPLY setting button we are getting this error which Muthu as mentioned.
"SRT Framework exception: Error in WSDL access: Exception occurred in communication framework:Error in HTTP Framework:404Connection Failed"
I have configured this in the past for some other project once where similar error(it was 402 or 403) was coming since WSDL node was not active under SRT in SRM but this time we have checked it and all the required services are also active.
Can you help to check further on this.
Regards.
Paresh.

Include own search help within new partner role (SRM 7.0)

Hi,
1) I have defined an own Partner Function and Partner scheme for Contracts.
2) I have defined an own table with partners and description (z-table).
3) I have defined an own search help including the own z-table.
4)I have included my own search help to the new defined partner scheme (spro --> cross application Basic settings --> Define partner schema --> partner determination procedure --> Search help name (own search help)
If I start a contract in the system, I can see my new partner Function within header data -> so far so good.
Also my own searchhelp is included, I can see the defined partners within my own z-table using F4 help.
Problem:
Partner ID and Description from Z-Table are not returned to Web Dynpro after selecting one partner from my result list.
Question:
How do i define a correct customer search function including an own table for partner functions/schema?
Do I have to use a search exit within my search help to return the Partner Id and Description correctly to the contract fields?
SRM standard seems to use the follwing exit:
BBP_F4IF_SHLP_EXIT_CLL_PARTNER
Any help concerning this issue is highly welcome
Thanks and best regards
Andreas

Hi
We can create the Contact person for the vendor with the following roles in SRM 7.0
SAP_EC_BBP_ADMINISTRATOR-->SAP SRM: Administrator
SAP_EC_BBP_PURCHASE-->mySAP SRM Purchaser
SAP_EC_BBP_ST_PURCHASER -->SAP SRM: Strategic Purchaser
Select the vendor created by you from the 'Business partner' page and click on 'Create Contact person'.
Enter the details required as per the requirement and save.
Regards,
Chandolu Ramesh

Distributing Central Contract from SRM to ECC

Hi,
We are using SRM 7.0 with ECC 6.0 in backend (no EHP). We're setting up a central contract with IDOCs. From what I read we have made the configuration:
in SRM:
- Assign attribute CT_PROC_TY = CCTR
- Connfigure new condition type PB00 which is the same with ECC price for contract
- activate the BADI BBP_DETERMINE_LOGSYS and coding it so for contract it will always go to backend (in method CONTRACT_LOGSYS_DETERMINE)
- I have activated BADI BBP_CTR_BE_CREATE but writing no code, as there no need for me to do mapping
in ECC:
- Activate inbound IDOC type BLAORD and COND_A and assign it to the logical system of SRM
Then I create the contract in SRM. but:
1. When creating contract, in item overview, i cannot tick 'distribution' indicator. Not sure what is the function
2. In item detail, tab distribution, I cannot put create release-purchasing org. Even when using search help it is not giving any value
Actually dont really understand the usefull of the indicator above, so I let it be empty, then I release the contract
The contract then not appear in ECC. I have checked SMQ1/SMQ2 nothing. Even in WE05 in ECC nothing. The only thing I see is in SLG1 where I see error triggered by user WF-BATCH with message "No recipient found"
Do i miss something in here? Any help will be very appreciated.
Josh

Hi Josh,
Central contract is only possible in SRM 7.0 with ECC 6.0 EHP 4. You can use local contracts or GOA.
Regards.

How to define a new partner function?

Dear experts!
Thank you for your attention!
we are using ECC6.0, I just want to ask how we can define or create a new partner function?
Best regard!
Tangdark

Hi
Tang
Use Tcode VOPA
Partner function
Specify an alphanumeric key which can have up to 2 characters and a description for a partner function.
Partner type
The partner type is an indicator which informs you of the type of partner, for example, partner type customer "KU".
Currently, you cannot change the partner types in customizing. You canonly select the partner types that are included in the standard SAP R/3 System.
Error group
Using the error group, you assign an incompletion procedure to a partner function (see section "Incompletion log").
Higher-level function
For a partner function, you can specify the higher-level partner
function. In this way, you can portray an existing dependency between the partner functions.
Unique in customer master record
If you characterize a partner function as unique, you can specify it only once in the customer master record.
The sold-to party has to be unique in the customer master record whereas you may specify several contact persons.
Customer hierarchy type
In this field you can specify whether a partner function can be used for a customer hierarchy. Enter the customer hierarchy type permitted
for the partner function. Refer to the section "Define hierarchy types
and assign to account groups".
Convert functions
If you work with several languages in the sales and distribution
system, you can carry out a language-dependent function conversion.
This means you can display the internal key definition, for example, AG, WE, and so on, differently on the screen depending on the logon language of the user. For example, you can display the key CU as AG when logged on in German. (The conversion is necessary because the partner functions such as AG, WE are partially hardcoded in the programs.)
Thx.
Edited by: DWARKESH THAKKAR on Oct 28, 2008 7:16 AM

Setup Central Contract Management SRM 7.01 with differing release versions

Hello experts,
OSS note 1268821 explains how to configure the central contract management between a SRM 7.0 and an ERP 6.04. So far so good, but how should it be handled if there are differing release versions such as ERP 6.04 and ERP 6.03? I guess that a technical split (xml services/ ALE distribution) is necessary?
Assuming that there are some backends with differing release versions and in some cases with differing master data (not supported by central master data client) would you always go via PI? Independent of release version, technology and master data.
Could you give some further detailed informations how to configure such a scenario? What has to be done to transfer existing contracts from an ERP 6.04 into SRM CM component (migration concept)?
Thanks!!!
KR Thorsten

Hi Thorsten
The minimal ECC version is 6.0 EHP4, Central Contracts require certain business functions in ECC to be activated and as these are included within ECC EHP4 you won't have these available in lower version. Therefore you won't be able to operate central contracts in such an ECC system.
You would either have to go with patching these systems or go with GOA's for these systems.
Operating central contracts via PI or SOA i believe provide almost similar functionality. SOA however requires an SRM EHP1 system and ECC EHP5 back-end to operate whilst central contracts configured via PI can be operated onwards from an SRM 7.0 and EHP4 system.
I can't help you on your migration issue, maybe someone else can.
Kind regards,
Tim

Central Contract -- Sch Agreements error in SRM7 -- ECC6 Eph4

Hello,
While creating a central contract in SRM7 and distribution to BE ECC6 Eph4. I am getting a condition mapping error in the IDOC.
Central contracts to contract in BE uses PI
Central Contracts to Sch Agreement in BE is IDOC.
I see an erro " Errors occured in Mapping operation for conditions data" When i check the FM META_CTR_CHECK .
Mapping conditions are maintained in the ECC
SPRO--> Integration with Other SAP components > Central Contracts> Maintain Conditions.
The same settings work in the development system. I see an entry with 003 Message number in table BBPD_CTR_IDOCREF.
Any help is appreciated. Thanks

Hi Netaji,
I know this has been closed for sometime now, I thought I should tell you that you can send central contract from SRM 7.01 to ECC 6.0 Ehp4 and above using non PI webservices.
Please find the link below just for your information
http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/06/13/transfer-of-central-contract-from-srm-to-ecc-using-web-services-without-pi
Regards,
Naveen

CONTRACT DISTRIBUTION CCTR Vs GOA

Hi All
Learnt that SAP has some improvement on DISTRIBUTION for CCTR contract ? Can any one explain how it is Indeed helps compare to GOA.
In GOA --> in the Header it self we go to distribute Porg, plant , Doc Type and Release value.
How new enhanced CCTR Contract Distribution works. I believe seperate folder for DISTRIBUTION in CCTR.
what steps needs to be followed on simple and comlex distribution?.
Muthu

Hi Muthu,
From what i know, CCTR can be referenced and used both in SRM and ECC, wheras, GOA can be used IN ECC only (after it is created and distributed from SRM).
Pricing would be controlled from SRM.
You need to activate Business Function, set the appropriate doc types and condition types in ECC.
CCTR Distribution / qty usage updates works using PI while GOA uses IDOCs.
Additional fields for say CCTR number / item number appear in ECC after Business function activation. You also need to add the workflow user in the Org structure (Local POrg/Pgrp).
Not sure on the Simple and Complex scenarios though.
Cheers - Akash

May Release: New partner support, Infrastructure updates, Site templates and bug fixes

Link: http://www.businesscatalyst.com/_blog/BC_Blog/post/May-release-New-partner-support-Infrast ructure-updates-Site-templates-and_bug-fixes/
We are announcing a new Business Catalyst release, scheduled to go live on Thursday, May 3rd. With this release, we are continuing our investments in system performance and stability by increasing our web servers capacity, enabling HTTP acceleration to provide faster site loading times, and improving the site creation speed by using pre-generated sites.
On the product side, we have completely revamped our partner support workflow taking advantage of the Adobe support infrastructure and tools, enhanced the site templates workflow for partners, and included lots of bug fixes and improvements. Read through the following sections to get detailed information about this release:
Partner support
Infrastructure updates
Features and enhancements
Issues fixed by this release
What's next
You can jump to the corresponding section by clicking the above links.
Partner support
Updated Help & Support partner experience
Following Adobe ID support, we have upgraded BC support tools (cases, chat, documentation) with standard Adobe tools. As a partner, you can now benefit from the same support tools as the rest of Adobe Creative Suite, and can track your support cases with Adobe BC, Dreamweaver, Muse or Photoshop in a single place.
Partners with more than 100 paid sites will get 2nd level chat support, which includes a higher priority, by default. If you have more than 100 paid sites, but spread across different Partner Portals, please ask support to enable 2nd level chat for you.
Support experience for your Small Business owner clients can now be owned by partners (see below).
Custom Help & Support URL for your clients
As a partner, you are probably already offering various additional services to your clients besides building & maintaining their BC site. Support, tailored specifically to your client needs, is usually one of these value-added services. We are now enabling you to take your Support service to the next level. In Partner Portal Settings, you have the option to set a custom URL for what will open when your client clicks on Help & Support inside Admin Console:
If you have multiple partner accounts, for different verticals, you can specify a Support URL for each of these.
The default Support experience provided by BC for your clients will be updated in a few releases to be similar to the partner support experience. This includes BC-branded support cases and documentation. If you'd like to keep a white-label experience for your customers, please set your own Help & Support URL in Partner Portal.
For more details please read the Improved support workflow and new forums announcement on our blog.
Infrastructure updates
Between our April release and the following infrastructure updates have been enabled
Limited trial sites for free partners – starting with our May release, the number of trial sites a Free Partner can have will be limited to 100. Once the limit is reached, Free Partners that need to create a new trial site have the options to upgrade to a higher partner plan, upgrade some of the trial sites to paid or delete unused/expired trials.
Automatic trial expiry extension - with this release, trial site expiry date will be automatically extended with 30 days every time an admin user logs in the system through the admin interface or through FTP.
Installed additional hardware - we have installed additional web servers on all our data centers, that translate into an increase of the existing capacity with over 70%.
Updated DNS infrastructure - we have improved the DNS resolution for email delivery so that we can increase the rate at which we're sending the system operational emails
HTTP acceleration – all sites static assets are served from a new cache engine (images, CSS and JavaScript files, together with improved headers that should allow the browser to cache them better for a browsing session). This update has been turned on along with our April release, and has made all the BC sites load faster on first and on subsequent loads.
Accelerated site/partner creation – we've changed the way new sites are created for faster speed, pre-creating them and reusing pre-created sites when needed, and have also improved the creation process for new partners, minimizing the impact of new CCM customers on the existing datacenters.
Adobe ID for partners - in order to support an integrating experience between the various Adobe tools a partner may use (Dreamweaver, Muse, Support forums) we have added Adobe ID support for Business Catalyst partner accounts. Starting April 19, partners are asked to merge their current Business Catalyst account with their Adobe ID accounts. For more details about the transition process and FAQ please read the Introducing Adobe ID blog post.
Updated Terms of Use - Along with several other changes in our processes in the past few months, we also revamped our Terms of Use and the signature process by requesting every admin user to sign a TOU. We have completed the rollout for partners, and we might be pushing an updated partner Terms of Use version within the following weeks. For more details and questions about this change, read the New Terms of Use for Business Catalyst blog post.
Features and enhancements
Site templates
To support the increasing number of partners building, sharing or reusing templates to create new sites, we're extending our site templates support from our partner portal with a new template type and improved management support. The update is going to enable partners to mark sites as templates and choose between making them available in Online Business Builder and keeping them private in their partner portal. A template site will not expire and has the same limits as any other trial site.
Based on your partner level, you can create private or public templates using the Site Details screen or the Tools>My Site Template section from your Partner Portal. Standard partners can only create private templates, while Free Partners can only view site templates that have been transferred to their accounts by other partners.
The number of templates a partner will have will be limited and will vary based on partner level: free partners can store up to 5 templates in their partner portal, standard partners have up to 100 site templates while Premium Partners might have up to 200 templates. Paid sites marked as templates are not counted against these limits.
Business Catalyst Partner fixes
While we are really focused on making the Business Catalyst integration into Creative Cloud a smashing success, we are slowly resuming our efforts to deliver fixes that have been requested by our partners. This release includes the following partner fixes:
Improved product custom fields - we have increased the maximum number of characters for product custom fields to 1024 (previous limit was 256); this gives partners and customers additional space to use when working with products
Improved Secure Zone subscribers list - we have added the customer email address in the Secure Zone Subscribers list to enable partners better filter and manage customers
Better experience when exporting data - to prevent customer confusion when exporting data from Mac computers, we have removed the export to excel option and exporting in CSV format by default.
Social plugins integration updates
Starting with our May release, we are updating the social plugins support to require users to get the plugin code from the third party provider and saving into his Business Catalyst website. The module tags and configuration will remain unchanged, but will render an empty tag until the partner or site owner will update the module template to include the corresponding module code snippet from the third party platform provider.
For more information about how you can enable the Social Plugins on a Business Catalyst websites, read the Social Media: Integrating Facebook and Twitter knowledge base article.
Other changes
Updated weekly emails - Starting with our May release, the information in the site weekly emails has been filtered based on the site's plan. For example, webBasics site reports will no longer include the sales report.
Localization - we improved and increased the coverage of the admin interface translations into German, French and Japanese
Site Settings -> Ignored IP addresses has been relocated under Reports -> Visitors -> More.
BC-Dreamweaver integration performance improvements
Development Dashboard has been removed, as it didn't provide a clear useful, ongoing benefit. The information present in the development dashboard has been integrated into our new Help & Support section.
Payment gateway settings - for more privacy and data protection, we have updated the Payment Gateway configuration screens to obfuscate the sensitive login information. Fields that have been obfuscated are now requiring confirmation.
Report abuse badge on trial sites - for compliance reasons, a "Report Abuse" link has been added to the front-end of all trial sites of free partners that don't have any paid sites. When they click the Report Abuse link, site visitors are redirected to a form submission page on businesscatalyst.com site.
Issues fixed by May release
Issues 3051303, 3168786 - Workflow notifications - Fixed a problem preventing workflow notifications emails from being sent.(see get satisfaction forum discussion)
Issue 3164074 - Fixed a bug causing the lightbox gallery created from Muse to be displayed behind page elements
Issue 3162810 - Fixed a bug in rendering engine to prevent content placed between body and head tags being incorrectly moved inside the body tag
Issue 3166610 - Fixed a broken link to Partner Portal in Internet Explorer
Issue 3175003 - Fixed an issue that caused an incorrect price display for the Year One-Off Setup Fee when upgrading a site from Admin using CB
Issue 2567278 - Fixed a bug causing site replication to ignore product attributes
Issue 2947989 - CRM passwords are now case sensitive
Issue 2723731 - Removed CSS files from the head section of the Layouts files, when downloaded and opened in Dreamweaver, via the BC extension
Business Catalyst new admin interface updates
Added "Save and Add New" button in Web App Item Add & Edit screens (see get satisfaction forum discussion)
Updated Quick Actions menus to add more actions (see get satisfaction forum discussion)
Fixed an issue causing Recent items menu to display deleted items (see get satisfaction forum discussion)
Fixed a display issue on File Manager making top buttons unreachable (see get satisfaction forum discussion)
Fixed the scrollbars in Email Marketing>Campaign>Stats>Bounced Emails reports (see get satisfaction forum discussion)
Fixed an issue causing Recent items menu to brake after selecting the current page from the Recent Items menu (see get satisfaction forum discussion)
Replaced the Success notification displayed when selecting Users or Permissions tabs from User Roles with an Warning
Change the action label displayed in User Roles list from View to Edit to match the list pattern from Admin Users
Fixed a missing file JavaScript error occurring when trying to open image manager from product details-> Attributes -> options
Moved System Emails section from Site Setting to Site Manager (see get satisfaction forum discussion)
Updated Domain Management interfaces to close the modal window and refresh the domain list after successfully adding a domain
Fixed an issue preventing the Hyperlink Manager to function properly (see get satisfaction forum discussion)
Updated the confirmation message received after copying a page to match the new workflow and button names
Fixed an issue causing the current screen or section to not be highlighted in the menu
Updated styling on the new dashboard, user management and email accounts interfaces
Updated dashboard reports filters and chart display; made the chart and the filter use the site time zone
Fixed an issue preventing users from inviting new admin users or create new email accounts on Internet Explorer 8
Fixed an issue preventing users from deleting Email Accounts or Admin Users in Internet Explorer 8
Fixed some issues preventing password recovery email from being sent
Removed the alert message displayed when the user or email account limit has been reached
Added localization for the simplified dashboard
Fixed display issues for site limits, domains and user list in the simplified dashboard
Added Custom reports for webBasics plan
Fixed a bug generating a "500:Collection error" on the simplified dashboard when user did not had View users permission
Added TOU checkbox in the email account setup screen
Updated Site Preview link in the dashboard to load the default domain
Fixed an issue in the new File Manager forcing a user to press Undo twice in order to see the change take effect if the code that was previously formatted contained any <"tag" with more than 2 lines
Fixed an issue causing the File Manager editor toolbar to incorrectly render if page URL path is longer than certain value; starting with this release, the site URL is trimmed
Fixed an issue causing the invite users to be displayed as [object Object] in dashboard and admin user list
Fixed a bug in the new admin causing the interface to become unresponsive when using the browser Back button
Fixed an issue in the new File Manager causing "Save Draft" button to publish the default page template instead of creating a draft version
Fixed a broken invite link issue in the Email Account invite email
Updated loading indicators in File Manager and Email Accounts screens
What's next
The first item on the what's next list might not be news for many of you, but it's definitely one of the most important milestones this year. The Creative Cloud launch is just around the corner, and Business Catalyst is playing an important role in that, as the publishing platform for Adobe® Muse and Dreamweaver. This launch will capture all our attention within the next weeks as we want it to be our best ever.
We'll start our next development cycle on May 15th, while the next Business Catalyst release is going to be pushed live in mid June. That being said, the following items are already on our launch plan for the next release and a few more will join the list. Please expect an update on our 2012 plans around mid May.
HTTP throttling – all page load and API calls to BC will be protected against attacks, this might trigger problems for API heavy sites. We are looking into enabling this update along with our June release, and will help make sure that a reasonable number of requests will be accepted from the same computer per minute.
Automatic site deletion - Starting with the June release, we are going to start automatically delete expired trial sites and canceled sites. Customers will be notified twice before we are going to proceed with deleting the sites.
Thank you,
Cristinel Anastasoaie
Adobe Business Catalyst Product Manager

In reference to this change in the Custom Reports... Better experience when exporting data - to prevent customer confusion when exporting data from Mac computers, we have removed the export to excel option and exporting in CSV format by default.
What is the customer confusion we are trying to stop here? I've got even more confused customers at the moment because all of a sudden they can't find the export to excel option but know it exists if they log in on a PC?
Mark

Central contract distribution trough IDOC - including new partner

Similar Messages

Maybe you are looking for